Repository navigation
Sync @minecraft/api-docs-generator to published 2.4.0 - #165
Merged
Merged
Conversation
The 10/09 release published @minecraft/api-docs-generator@2.4.0 to npm, but postpublish failed (expired REPO_PAT), so the version bump was never pushed back. Subsequent releases try to re-publish 2.4.0 and fail validation. Apply the bump beachball would have committed and raise markup-generators-plugin's dependency range to ^2.4.0. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Fail the release early if REPO_PAT is invalid, expired, or lacks write access, before anything is published to npm. Previously an expired PAT failed postpublish after the npm upload, leaving npm ahead of the repo. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
rlandav
approved these changes
Oct 13, 2026
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
2 participants
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.
Fixes the failing Release Changes workflow (e.g. run 38417777682).
What happened
@minecraft/api-docs-generator@2.4.0to npm.postpublishstep, which creates the GitHub release, failed withHttpError: Bad credentialsbecauseREPO_PAThad expired. The run then failed, so the version bump and change-file cleanup were never pushed tomain.This change
npx beachball bump --scope tools/api-docs-generator): version 2.4.0, CHANGELOG entries, and removal of the two api-docs-generator change files.markup-generators-plugin's dev and peer dependency range to^2.4.0, matching what previous release commits did.api-docs-generatorhas no changes since 88f54aa, the commit 2.4.0 was published from, somainmatches what's on npm.The
markup-generators-pluginchange files are kept, so the next release will publish only@minecraft/markup-generators-plugin@2.3.0.REPO_PAThas already been rotated. The@minecraft/api-docs-generator_v2.4.0GitHub release/tag is still missing and can be created manually if wanted.Prevention
Verify REPO_PATstep right after checkout inrelease-changes.yml. It callsgh api repos/$GITHUB_REPOSITORYwithREPO_PATand fails the run, with a clear error, if the token is invalid or expired or lacks write access. This happens before the build and before anything is published to npm, so a bad token can no longer leave npm ahead of the repo. Failures still go through the existingHandle failurenotification.