Repository navigation
Fix paginated release API collection - #442
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
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.
Release preparation stops before signing because GitHub CLI rejects combining
--slurpwith--jq. Collect paginated responses first, then flatten them with the existing Python runtime. Apply the correction to release job/artifact collection and apt bootstrap deployment history, preserving all tag, source and independent-review gates.The regression executes the actual workflow commands against multiple and empty pages, malformed JSON, and an API failure after valid output. It fails with the original commands; all 10 focused release authorization, inventory and pagination tests pass on Linux.
Related to #275.