Fix release staging and cleanup guards - #44
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
New emailaccessible nameHQBase/hqbaseexplicitly when the job has no checkoutRoot cause
Signed release workflow run #19 installed 0.1.14, applied the exact signed 0.1.15 candidate, and verified its release marker. The lifecycle retry then reached the authenticated flow but waited for the removed
Composeaccessible name. Its cleanup job also rangh release deletewithout repository context, so I removed that failed draft through the repository UI after confirming it was never published.Validation
CI=true WRANGLER_LOG_PATH=/tmp/hqbase-release-0.1.15-final-fix-check-wrangler.log pnpm checkCI=true WRANGLER_LOG_PATH=/tmp/hqbase-release-0.1.15-final-fix-dry-run-wrangler.log pnpm deploy:dry-runnode scripts/check-docs.mjsv0.1.15absent before rerun