Skip to content

fix(ci): pin npm and make provenance explicit in npm publish #53

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
johnpmitsch merged 1 commit into from
Jul 10, 2026
Merged

fix(ci): pin npm and make provenance explicit in npm publish #53

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 7 additions & 4 deletions .github/workflows/publish-npm.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,8 +27,11 @@ jobs:
node-version: '24'
registry-url: 'https://registry.npmjs.org'

- name: Ensure npm supports trusted publishing
run: npm install -g npm@latest
# Pin npm rather than tracking @latest: some published npm releases ship a
# broken bundled `sigstore` that crashes provenance generation with
# MODULE_NOT_FOUND. 11.6.2 has a working sigstore and supports trusted publishing.
- name: Install pinned npm
run: npm install -g npm@11.6.2

- name: Download node .node artifacts from GitHub release
run: |
Expand Down Expand Up @@ -122,9 +125,9 @@ jobs:
run: |
for pkg_dir in */; do
echo "Publishing $pkg_dir"
(cd "$pkg_dir" && npm publish --access public --tag "${{ inputs.npm_tag }}")
(cd "$pkg_dir" && npm publish --access public --provenance --tag "${{ inputs.npm_tag }}")
done

- name: Publish main package
working-directory: npm
run: npm publish --access public --tag "${{ inputs.npm_tag }}"
run: npm publish --access public --provenance --tag "${{ inputs.npm_tag }}"
Loading