Repository navigation
chore: release 0.2.0 with npm trusted publishing - #2
Merged
Merged
Conversation
Bump the package, crate, and loader to 0.2.0 and publish v* tags with OIDC instead of an NPM_TOKEN. Co-authored-by: kellas <alex.step.kellas@gmail.com>
alexstep
marked this pull request as ready for review
October 7, 2026 23:23
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.
Summary
Prepares 0.2.0 and switches tag publishing to npm Trusted Publishing (OIDC). Nothing was published, no tag or GitHub release was created, and
mainwas not pushed.package.json,Cargo.toml,Cargo.lock, and the version checks inindex.jsare0.2.0.npm/are generated, not committed (.gitignore).napi create-npm-dirs/napi versionwrite0.2.0into all 12 of them. The publish job checks that beforenpm publish..github/workflows/release.ymlpublish job:permissions: id-token: writeandcontents: read, Node 24,registry-url: https://registry.npmjs.org,npm install -g npm@11with a hard fail below 11.5.1. NoNPM_TOKENorNODE_AUTH_TOKEN.prepublishOnlystill runsnapi prepublish, which shells out tonpm publishin eachnpm/<platform>directory with the job environment. npm uses OIDC before any token, so those publishes do not need a token or.npmrcauth.v*tag that does not matchpackage.jsonfails incheck-versionbefore the prebuild matrix, and again at the start of the publish job.release.yml.npm stage publishonly. Enable directnpm publishfor this workflow.Packages that already exist on npm (0.1.5)
Trusted Publishing can be configured for all of these. None would be a first publish.
@alexstep/doc-extract@alexstep/doc-extract-win32-x64-msvc@alexstep/doc-extract-win32-ia32-msvc@alexstep/doc-extract-win32-arm64-msvc@alexstep/doc-extract-darwin-x64@alexstep/doc-extract-darwin-arm64@alexstep/doc-extract-linux-x64-gnu@alexstep/doc-extract-linux-x64-musl@alexstep/doc-extract-linux-arm64-gnu@alexstep/doc-extract-linux-arm64-musl@alexstep/doc-extract-linux-arm-gnueabihf@alexstep/doc-extract-freebsd-x64@alexstep/doc-extract-wasm32-wasiNot done
npm publish, nov0.2.0tag, no GitHub release.