fix: enable npm OIDC publishing + reliable release tag pushes - #4
Merged
Conversation
Publish workflows failed at 'npm publish' with a masked 404 (unauthorized): trusted publishing (OIDC, used here via --provenance with no NPM token) requires npm CLI >= 11.5.1 and Node >= 22.14.0, but the workflows ran Node 20 / npm 10.x. Bump publish workflows to Node 22 and upgrade npm to latest before publishing. Also fix the release flow so tag pushes actually trigger workflows: GitHub creates no push events when more than 3 tags are pushed at once, and lerna pushed all tags together. Set lerna command.version.push=false and push each tag in its own 'git push' (push:release), one event per tag.
Packages referenced github.com/ScreebApp/sdk-js (and sdk-reactnative its own repo). Align repository/bugs/homepage URLs to the actual repo ScreebApp/sdk so npm provenance source matches the building repo.
Alexays
pushed a commit
that referenced
this pull request
Jul 9, 2026
fix: enable npm OIDC publishing + reliable release tag pushes
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #3. After #3 the publish workflows finally triggered on the lerna-format tags — but all 5 then failed at
npm publish, and a normal multi-package release still wouldn't trigger them at all. This fixes both.1. npm publish failed: trusted publishing needs newer npm/Node
The runs got:
A 404 on PUT to an existing package = unauthorized (npm masks 401/403 as 404). The workflows publish tokenlessly via OIDC trusted publishing (
--provenance,id-token: write, no NPM token). Per npm docs, trusted publishing requires npm CLI ≥ 11.5.1 and Node ≥ 22.14.0 — but the workflows ran Node 20 / npm 10.x, so the publish fell back to (absent) token auth.Fix: bump the 5 JS publish workflows to
node-version: '22'and addnpm install -g npm@latestbefore publishing.2. Multi-package releases didn't trigger any workflow
GitHub: "Events will not be created for tags when more than three tags are pushed at once." The
chore(*): publishrelease created 7 tags and lerna pushed them together, so zero push events fired.Fix: set
command.version.push: falseinlerna.jsonand push each tag in its owngit push(push:releasescript) — one push event per tag, always under the limit. The release entrypoint staysnpm run version, soCONTRIBUTING.mdis unchanged.After merge
The 5 pending versions (sdk-browser@0.6.1, sdk-react@0.7.1, sdk-angular@0.6.1, sdk-vue@0.2.1, react-native@3.3.1) still need publishing. Their tags currently point at the pre-fix commit, so they must be re-pointed to merged
master(which has the fixed workflows) and re-pushed individually to publish. Nothing is on npm yet, so no version is burned.Note (not fixed here)
npm publishwarns the packages'repository.urlnormalizes togithub.com/ScreebApp/sdk-jswhile this repo isScreebApp/sdk. Worth aligning so provenance source matches the build repo.