Repository navigation
ci: use the organization NPM_TOKEN for automatic releases - #17
Merged
Merged
Conversation
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.
Use the existing organization
NPM_TOKENfor automatic npm publishing, with the legacyNO_TWOFA_NPM_TOKENas a fallback. Keep OIDC available for a later trusted-publisher setup. Tokens are exposed only to the registry access, publish, and verification steps.The organization token currently allows private repositories only, while this repository is public. It must be made available to
traceflow-sdk, or provided as a repository secret, before publishing. Document this prerequisite and token renewal alongside the optional trusted-publisher setup.Validation: actionlint and git diff checks. SDK behavior and release-selection logic are unchanged.