Repository navigation
ci: publish to npm with trusted publishing (OIDC) - #10
Closed
mvantellingen wants to merge 1 commit into
Closed
mvantellingen wants to merge 1 commit into
mvantellingen wants to merge 1 commit into
Conversation
|
mvantellingen
force-pushed
the
npm-oidc
branch
from
October 25, 2026 18:59
fb98503 to
c9f220c
Compare
mvantellingen
changed the title
mvantellingen
added a commit
that referenced
this pull request
Oct 26, 2026
Supersedes #10 (rebuilt on top of main). Publish through changesets/action v2 with npm trusted publishing and provenance instead of an NPM_TOKEN, run the release job in the release environment without a dependency cache and set up Node/pnpm via labd/gh-actions-typescript. Also run the validation on pull requests instead of on every push.
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
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.
npm trusted publishing
The org-level
NPM_TOKENsecret is gone, so releases now publish through npm trusted publishing (OIDC), followinglabd/commercetools-node-mock.releasejob:environment: release, withid-token: write,contents: writeandpull-requests: write^11.6.4; pnpm 8 publishes through the npm CLI.NPM_TOKEN/NODE_AUTH_TOKENchangesets/actionv1.7.0 -> v2.1.2 (inputs renamed), withpush-with-git-cli: trueandNPM_CONFIG_PROVENANCE: truepackage.json:repository.urlis nowgit+https://github.com/labd/js-toolkit.gitandpublishConfig.provenanceistrueBefore merging, add a trusted publisher on npmjs.com for
@labdigital/toolkit. Use repositorylabd/js-toolkit, workflowrelease.ymland environmentrelease.