Repository navigation
Fix draft release lookup and prepare Anomalyzer 0.2.1 - #3
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.
The first tagged release passed every package and offline Lambda check, then failed after creating its draft because GitHub's release-by-tag endpoint does not return drafts. Discover drafts through the authenticated paginated release list, resume without duplicate creation, and verify final immutability through the release ID.
Prepare 0.2.1 without moving the existing v0.2.0 tag or changing its unpublished draft. Update the release and consumption guide while retaining README progression chapters 14–22 and their published examples.
Validation: 215 tests pass locally, including regressions for draft creation, resumption and final ID lookup. The fixed read-only lookup also finds the actual v0.2.0 draft.