Repository navigation
Restore /snapit using workflow dispatch - #8721
Merged
Merged
Conversation
gonzaloriestra
marked this pull request as draft
October 1, 2026 09:10
gonzaloriestra
marked this pull request as ready for review
October 1, 2026 09:28
isaacroldan
approved these changes
Oct 2, 2026
1 of 4 tasks
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
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.
WHY are these changes introduced?
npm no longer allows Trusted Publishing from
issue_commentworkflow runs, so/snapitcannot publish snapshots directly.WHAT is this pull request doing?
Keep
/snapitby dispatching a separate release run on the default branch. The publisher checks the original comment, the requester's write permission, and the current PR commit before runningpnpm release snapshot. Fork PRs remain unsupported. The snapit action is no longer used.Report the installation command or failure on the PR. Existing manual and scheduled releases keep their current behavior. No new secrets or npm configuration are required.
How to manually test your changes?
Merge and /snapit
Checklist
patchfor bug fixes ·minorfor new features ·majorfor breaking changes) and added a changeset withpnpm changeset add