docs(changelog): cut v0.5.0 - #138
Merged
Merged
Conversation
Everything since v0.4.2 becomes 0.5.0: a minor bump, not a patch, because the line carries breaking removals — the Apple Containers backend, checkpoint/restore with the Podman backend, the per-backend capability gating, and the `compose.Plan.Validate` signature. Also backfills the 0.4.3 section. v0.4.3 was tagged at #120 (UpOptions.AdoptExisting) without a changelog cut, so that release shipped with no entry and the compare-link chain skipped it, pointing Unreleased at v0.4.2 while a later tag existed. The entry is written from the shipped behaviour and the chain is repaired. Co-Authored-By: Claude Opus 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
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.
Cuts the
Unreleasedline as v0.5.0, and backfills the 0.4.3 section that was never written.Why 0.5.0 and not 0.4.4
The line carries breaking removals, so a patch bump would be wrong even pre-1.0:
--runtime applecontainervalue (feat!: remove the Apple Containers backend #127)runtime/podmanbackend (feat!: remove checkpoint/restore and the Podman backend #124)runtime.Capabilitiescut from six fields to three,compose.Plan.Validatelosing itsbackendNameparameter, and threeruntimeerror types (refactor!: remove the per-backend capability gating #128)On top of those:
EngineOptions.DisableHostPortPublishing(#137), the compose lifecycle-hook refusal, the hoisted §2.2 validation, theservice_healthygate fix, and the dependency and CI bumps (#129).The 0.4.3 backfill
v0.4.3was tagged at #120 (UpOptions.AdoptExisting) without a changelog cut. Two consequences, both fixed here:[Unreleased]compared againstv0.4.2whilev0.4.3existed, so the "unreleased" diff silently included a shipped release.The entry is written from the shipped behaviour (commit
e46401a), dated at the tag's commit date (2026-08-24), and the chain now runsv0.4.2 → v0.4.3 → v0.5.0 → HEAD.I did not fold #120 into 0.5.0 — it shipped in 0.4.3, and moving it would misreport which release users got it in.
After merge
The tag still needs pushing at the merge commit:
git tag v0.5.0 <sha> && git push origin v0.5.0. I have not tagged anything — say the word and I'll push it, or it's yours.Recent tags (
v0.4.1,v0.4.2,v0.4.3) have no GitHub release object; the last one isv0.4.0. I've followed that convention and not prepared one — worth saying if you'd rather this release got one, given it's the first with breaking changes since.🤖 Generated with Claude Code