fix(ci): use default GITHUB_TOKEN for changesets changelog step#3
Merged
Conversation
The Release workflow failed at `changeset version` because
@changesets/changelog-github's GraphQL request fails when authenticated with
the vland-bot App token — GitHub closes the response mid-body ("Premature
close"). The default token completes the same request.
Switch the changesets/action GITHUB_TOKEN to ${{ secrets.GITHUB_TOKEN }}.
The App token still authenticates actions/checkout, so the version-branch,
tag, and publish pushes keep triggering downstream workflows.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
Contributor
Preview releaseLatest commit: Some packages have been released:
Note Use the PR number as tag to install any package. For instance: |
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.
Problem
The
Releaseworkflow fails atchangeset version.@changesets/changelog-github's GraphQL request fails when authenticated with the vland-bot App token — GitHub starts the response and closes it mid-body, surfacing as:Fix
Point the
changesets/actionGITHUB_TOKENat the default${{ secrets.GITHUB_TOKEN }}, which completes the same GraphQL request.actions/checkoutstill uses the App token, so the version-branch / tag / publish pushes keep triggering downstream workflows and pass branch protection.How it was isolated
Contents/Pull requests/Metadataread permissions confirmed in place → identicalPremature close..node-version=24).changeset version(same changelog-github generator) locally with a valid token succeeds and generates the changelog. The only differing variable is the token.Caveat
The
chore: update versionsPR is now created bygithub-actions[bot], so thepull_requestCI won't run on that bot PR. Everything else (push reach, publish, GitHub release) is unaffected.🤖 Generated with Claude Code