ci: use GH_PACKAGES_TOKEN fallback for release/snapshot publish#15
Open
ci: use GH_PACKAGES_TOKEN fallback for release/snapshot publish#15
Conversation
added 6 commits
March 1, 2026 22:25
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 hardening for publish workflows.
Changes
release.yml: useGH_PACKAGES_TOKEN(fallback toGITHUB_TOKEN) for:ci.ymlsnapshot publish path: same token strategy for versioning and publish auth.Why
Main release run failed with package publish permission errors using default token. This enables org-level package publishing via a dedicated secret when configured.
Operational note
Set repository secret:
GH_PACKAGES_TOKENwith package publish permissions fornpm.pkg.github.comWorkflow still falls back to
GITHUB_TOKENif the custom secret is absent.