Run details

virtualWorkspace

CI Pipeline Executions
- Current executionSucceeded
  v3.0.0-rc.0
- Runs and Agents
- Configuration
- Self-Healing CI
- Project Graph
- Circular DependenciesEnterprise
- Resource Usage
- Analysis
- ConformanceEnterprise
Runs

Insights

Compare tasks
Analytics

fix(publish): authenticate pnpm publish via ~/.npmrc, not a URL-scoped env var (RIG-2187) (#3) The first tagged publish of @rigelbuild/solid-virtual@3.0.0-rc.0 failed with a 404 on the PUT: the publish went out unauthenticated. Root cause: the auth token was passed as a GitHub Actions step env var literally named `pnpm_config_//registry.npmjs.org/:_authToken`, but Actions env-var names may only contain [A-Za-z0-9_] — a name with `/`, `:` and `.` is never exported to the step, so pnpm never received the credential and npm answers a scoped unauthenticated write with 404 (not 401). The clean-named `pnpm_config_provenance` exported fine, which is why only auth broke. Fix (source-verified against pnpm 11.9.0): write the per-registry `//registry.npmjs.org/:_authToken` into the user-level `~/.npmrc` from the clean-named `NPM_TOKEN` secret before `pnpm publish`. pnpm's credential reader (getNetworkConfigs -> configByUri) consumes the user npmrc unconditionally, so the token reaches the publish request. The npmrc is written on the CI runner only, so the upstreamable package diff (DL-015) is untouched. Provenance stays off via the env key and job permissions stay `contents: read` (no OIDC). Nothing was published on the failed run (404 = create rejected), so 3.0.0-rc.0 is not burned; re-tag re-triggers the publish.

nx run-many --targets=test:sherif,test:knip,test:docs,test:eslint,test:lib,test:e2e,test:types,test:build,build

Succeeded

4 CPU cores

176420d4v3.0.0-rc.0

Get faster results

Learn how to enable distribution.

Atomizer enabled

69 groups of tasks optimized.

© 2026 - Nx Cloud

Terms of Service Privacy Policy Changelog Status Docs Contact Nx Cloud Pricing Company @NxDevTools

virtualWorkspace