Repository navigation
chore: reset release-please and fix publish pipeline gaps - #20
Merged
Merged
Conversation
Two concrete pipeline fixes on top of the manifest/CHANGELOG reset: 1. release-please-config.json: add "force-tag-creation": true. Without this, release-please creates the GitHub release as draft (because draft: true) but does NOT push the underlying git tag ref — GitHub only creates the tag when the release is un-drafted. That deadlocks release.yml, which triggers on tag push. Matches the working ghd-test config. 2. release.yml verify-draft-release: bump contents: read to write. The Releases API returns 404 for draft releases when queried with contents: read. Our wait-for-draft-release.sh needs write-level access to view the draft. Other jobs already had contents: write. Also resets the stuck state from the previous attempt: - .release-please-manifest.json: back to 0.0.0. - CHANGELOG.md: delete; release-please will regenerate it. Out-of-band cleanup done before this PR: draft v1.0.0 release deleted, v1.0.0 tag (manually created and useless without the fixes) deleted, PR #19 closed, autorelease:tagged stripped from merged PR #18. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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.
Why
The first v1.0.0 release attempt (via PR #17's reset + PR #18 merge) shipped a draft release but never pushed the underlying git tag. `release.yml` triggers on tag push, so the whole pipeline deadlocked.
Two root causes:
Also resets state that PR #18's merge re-bumped:
Out-of-band cleanup already completed:
Test plan
🤖 Generated with Claude Code