chore: reset release-please state to re-cut v1.0.0 - #17
Merged
Merged
Conversation
Release-please merged the original v1.0.0 PR but failed to push the actual git tag because the meigma-release-please App was not in the tag ruleset's bypass list. That left master with manifest=1.0.0 and a populated CHANGELOG.md, but no v1.0.0 tag and a stale "untagged" draft release on GitHub. This commit re-seeds the release-please state so the next run proposes v1.0.0 fresh: - repository-settings.toml: uncomment the App bypass for the tag ruleset, expressed as type="integration" with the explicit App ID (3342783) so the configure script works without App-authorized tokens. Intent comment preserved above. - .release-please-manifest.json: revert "." back to 0.0.0. - CHANGELOG.md: delete; release-please will regenerate it. Live state already updated: ruleset bypass pushed via configure script; draft v1.0.0 release deleted; release-please's v1.1.0 PR (#14) closed; autorelease:tagged label stripped from merged PR #9. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
1 of 5 tasks
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.
Summary
Why
When PR #9 merged, release-please bumped the manifest + populated CHANGELOG.md but failed to push the `v1.0.0` git tag because the App was blocked by the tag ruleset. That left master in a stuck state:
Release-please then helpfully opened PR #14 proposing v1.1.0, compounding the confusion.
Out-of-band cleanup already done:
After this PR merges, release-please should open a fresh `chore(master): release 1.0.0` PR. Merging that will create the v1.0.0 tag, which will fire `release.yml`, which will build + attest + un-draft the release.
Test plan
Followup
The configure_github_repo.py script uses PATCH for ruleset updates, which returned 404 even with `admin:org` scope and repo admin. PUT to the same endpoint worked. Worth investigating separately; not blocking this PR.
🤖 Generated with Claude Code