Allow npm release recovery branches - #38
Merged
Merged
Conversation
ejsmith
marked this pull request as ready for review
July 29, 2026 00:50
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
release/npm/<version>branches to invoke the npm/GitHub Packages recovery pathWhy
The v1.3.4 npm release needs a recovery run after fixing its provenance metadata. The connected GitHub integration cannot invoke
workflow_dispatch, but authenticated Git push access is available. Arelease/npm/1.3.4branch provides the same explicit, version-scoped trigger without moving the existing tag or republishing JSR.Validation
deno task format-checkgit diff --checkrefs/heads/release/npm/1.3.4resolves to1.3.4