Repository navigation
docs: streamline the release PR merge steps in the releasing skill - #329
Merged
Merged
Conversation
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.
Summary
This PR changes the "Merge a release PR" steps of the
releasing-packagesskill. The changes come from the merge of #328:npm trust list. The agent shell has no npm login, so that command fails with E401. Thepublishjob publishes only through OIDC, so a package that it released before has a trusted publisher. The step now usesnpm viewto find new packages.gh run watchin the background. Thepublishjob can wait 20 minutes until npm shows each version, which is longer than the agent's foreground command limit.Checklist
nextbranch.!and aBREAKING CHANGE:footer.