fix(ci): service-auth-publish install-check 401 (missing GITHUB_TOKEN) - #879
Merged
Merged
Conversation
…ghbor documented The real publish succeeded on the first run (confirmed: @izzywdev/fuzefront-service-auth@0.1.0 now in the registry via `gh api users/izzywdev/packages/npm/fuzefront-service-auth/versions`), but the "Verify it is actually installable" step 401'd -- it only set NODE_AUTH_TOKEN, missing the GITHUB_TOKEN the project-level .npmrc actually reads (the exact failure mode the Publish step's own adjacent comment already documents). Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session-Id: fe3aa738-cb24-4315-a29b-29834ddea892
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.
Summary
service-auth-publish.yml(triggered by tagservice-auth-v0.1.0) succeeded through the actualPublishstep — confirmed viagh api users/izzywdev/packages/npm/fuzefront-service-auth/versionsshowing0.1.0now live in the registry.NODE_AUTH_TOKEN, notGITHUB_TOKEN— the exact failure mode the neighboringPublishstep's own comment already documents (the project-level.npmrcreferences${GITHUB_TOKEN}, which outranks theNODE_AUTH_TOKEN-only.npmrcsetup-nodewrites).GITHUB_TOKENalongsideNODE_AUTH_TOKENin that step'senv.Test plan
actionlintcleanservice-auth-publish.yml(viaworkflow_dispatch, since0.1.0is already published and idempotent) to confirm the verify step now passes — pending merge🤖 Generated with Claude Code