Repository navigation
fix: use compatible GitHub release pagination flags - #5
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
The first package Release run stopped before tag creation because GitHub CLI does not support combining
--slurpand--jq. Parse the paginated JSON with JavaScript instead. Package publication already succeeded; this changes only the release-list lookup and never republishes immutable 0.0.1 versions.Validation
pnpm qualitypasses, including installed tarballs and workflow security tests.gh api --paginate --slurpsucceeds against the real releases endpoint.Merge after green checks as part of the authorized 0.0.1 release, then dispatch only the package tag/Release workflows against the already-published source commit.