The Release job has failed on every push to main since 12:03:05 UTC today (7 consecutive runs, one currently in progress) -- the same root cause #858 tracked for rtf-codec, now recurring for a different, brand-new package.
@exadev/semantic-release-workspace releases packages in topological order and aborts the whole job the instant one package's own verifyConditions step fails. excel-number-format (a new foundation package, first published-to-npm attempt) is 4th in the current release order, right after archive-codec/byte-codec/document-schema.js, all of which succeed. Its own OIDC verifyConditions step then fails:
[semantic-release] [npm] Verifying OIDC context for publishing from GitHub Actions
[semantic-release] [npm] OIDC token exchange with the npm registry failed: 404 OIDC token exchange error - package not found
[semantic-release] ENONPMTOKEN No npm token specified.
npm's OIDC trusted-publishing token exchange requires an existing package record to attach a trusted-publisher config to -- a brand-new package name has never published before, so there's nothing to attach to, and the exchange 404s. This is a genuine npm/OIDC constraint (documented at https://docs.npmjs.com/trusted-publishers), not a workflow misconfiguration, and it needs the identical one-time, user-only remediation #858 needed for rtf-codec.
Impact: every package listed after excel-number-format in the current topological order (doc-codec, document-outline.js, epub-codec, markdown-codec, odf.js, ooxml.js, pdf-codec, ppt-codec, rtf-codec, wpd-codec, xls-codec, documents.js, document-cli, document-compute.js, document-mcp, documents) has not published a new version since this started, despite real feature work merging to main throughout: npm view excel-number-format version returns 404 (never published at all), confirming the blocker is live right now.
Remediation (same as #858, npmjs.com account-owner action only): sign in to npmjs.com -> Packages -> excel-number-format -> Settings -> Trusted publisher -> GitHub Actions -> Organization ExaDev, Repository documents.js, Workflow filename ci.yml, no environment. The first release after that publishes excel-number-format automatically, unblocking every package queued behind it.
Once excel-number-format is registered, re-running the Release job (or waiting for the next push to main) should publish the full backlog in one pass, since nothing downstream has actually failed its own release decision -- it's never been attempted.
The Release job has failed on every push to main since 12:03:05 UTC today (7 consecutive runs, one currently in progress) -- the same root cause #858 tracked for rtf-codec, now recurring for a different, brand-new package.
@exadev/semantic-release-workspace releases packages in topological order and aborts the whole job the instant one package's own verifyConditions step fails. excel-number-format (a new foundation package, first published-to-npm attempt) is 4th in the current release order, right after archive-codec/byte-codec/document-schema.js, all of which succeed. Its own OIDC verifyConditions step then fails:
npm's OIDC trusted-publishing token exchange requires an existing package record to attach a trusted-publisher config to -- a brand-new package name has never published before, so there's nothing to attach to, and the exchange 404s. This is a genuine npm/OIDC constraint (documented at https://docs.npmjs.com/trusted-publishers), not a workflow misconfiguration, and it needs the identical one-time, user-only remediation #858 needed for rtf-codec.
Impact: every package listed after excel-number-format in the current topological order (doc-codec, document-outline.js, epub-codec, markdown-codec, odf.js, ooxml.js, pdf-codec, ppt-codec, rtf-codec, wpd-codec, xls-codec, documents.js, document-cli, document-compute.js, document-mcp, documents) has not published a new version since this started, despite real feature work merging to main throughout:
npm view excel-number-format versionreturns 404 (never published at all), confirming the blocker is live right now.Remediation (same as #858, npmjs.com account-owner action only): sign in to npmjs.com -> Packages -> excel-number-format -> Settings -> Trusted publisher -> GitHub Actions -> Organization
ExaDev, Repositorydocuments.js, Workflow filenameci.yml, no environment. The first release after that publishes excel-number-format automatically, unblocking every package queued behind it.Once excel-number-format is registered, re-running the Release job (or waiting for the next push to main) should publish the full backlog in one pass, since nothing downstream has actually failed its own release decision -- it's never been attempted.