chore(main): release 0.8.0 - #29
Closed
ruby-automation wants to merge 1 commit into
Closed
Conversation
5 tasks
bougyman
added a commit
that referenced
this pull request
Aug 9, 2026
…y loop (#30) ## Summary `draft:true` (#18/#19) desynced release-please's own tracking from GitHub's actual release state once we published drafts ourselves via a raw `gh release edit --draft=false`, outside release-please's own process. Every subsequent run re-included already-released commits and kept bumping minor forever (0.2.1 -> 0.3.0 -> 0.3.1 -> 0.4.0 -> 0.5.0 -> 0.6.0 -> 0.7.0 -> a pending 0.8.0 PR). Split release-please's responsibilities into two workflows: - **`release-pr.yaml`**: runs on every push to `main`, `skip-github-release: true` - manages the version-bump PR only (manifest/CHANGELOG.md/`app/mix.exs`), never touches tags/releases at all, so it has nothing left to get confused about. - **`release.yaml`**: triggers only when that PR merges (`pull_request: closed` filtered to `release-please--branches--main` merging - approving the release *is* the trigger, not every push). Builds the Burrito binaries/tarballs/checksums first, reads the version straight from the manifest `release-pr.yaml` already bumped, then creates the tag + release + uploads every asset in one atomic `gh release create` call. No separate release object ever sits around waiting for a later upload, so Immutable Releases (GA Oct 2025, the reason #18 existed) never gets a chance to lock us out. Also reverts `.release-please-config.json`'s `draft: true` - unused now that release-please never creates the release itself. `burrito-release.yaml` is removed; its steps are folded directly into `release.yaml`. **Follow-up needed after this merges**: close the stray "chore(main): release 0.8.0" PR (#29), opened under the old broken setup, and let release-please regenerate a clean one against this new pipeline. ## Test plan - [x] Both new/edited workflow YAML files validated with `ruby -ryaml` (not python - not reliably available) - [x] Verified `skip-github-release` is release-please-action's real, documented input (checked its actual `action.yml` + README directly, including the exact migration-table semantics: this is what the old `release-pr` command did) - [x] Verified release-please-action's own README documents the identical "build artifacts, run release-please, gh release upload if release_created" pattern we're now using (minus its release-creation step, which we do ourselves) - confirms this is well-trodden, not novel - [x] Manually tested the exact version-extraction one-liner against the real `.release-please-manifest.json` - [ ] Next real release-please PR merge should build binaries, create exactly one tag/release with all assets attached, and not trigger any further automatic version bump 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Sonnet 5 <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
2 participants
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.
🤖 I have created a release beep boop
0.8.0 (2026-08-09)
⚠ BREAKING CHANGES
Features
Bug Fixes
Performance Improvements
Documentation
This PR was generated with Release Please. See documentation.