chore: release 0.5.1 - #134
Merged
Merged
Conversation
Step 1 of docs/releasing.md: drop the .devN suffix that main carries between releases and move the Unreleased entries under the new heading. No tag and no publish here — release.yml compares the tag to pyproject.toml exactly, so the version must land on main first. - pyproject.toml: 0.6.0.dev0 -> 0.5.1 (single source of truth; bambu_cli.constants.VERSION resolves from package metadata). - CHANGELOG.md: Unreleased kept as an empty heading; its Fixed bullets (the first-run person path, honest --confirm / --sim / go copy, and the print-errors-once fix) move under [0.5.1] - 2026-08-28. Older sections untouched. Footer gains the [0.5.1] compare link and [Unreleased] now compares from v0.5.1. uv.lock is deliberately untouched: it still records 0.5.0, but `uv sync --frozen` and `uv export --frozen` both pass with it, so nothing in CI forces the churn into this release PR.
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
Step 1 of docs/releasing.md for 0.5.1.
maincarries a.devNsuffix between releases, andrelease.ymlcompares the tag topyproject.tomlexactly — av0.5.1tag against a0.6.0.dev0version fails the build. So the version has to land onmainbefore the tag exists.Everything shipping in 0.5.1 is already on
main: the first-run person path and the honest--confirm/--sim/gocopy (#133, squash-merged as21445c4).What
Two files, five lines.
pyproject.toml:version = "0.6.0.dev0"→"0.5.1". Single source of truth —bambu_cli.constants.VERSIONresolves from package metadata.CHANGELOG.md:## [Unreleased]kept as an empty heading; its### Fixedbullets move under## [0.5.1] - 2026-08-28. No older section rewritten. Footer gains[0.5.1]: …/compare/v0.5.0...v0.5.1, and[Unreleased]now compares fromv0.5.1.No tag, no publish, no
0.6.0.dev0bump — those are steps 2 and 6, after this merges.uv.lockis deliberately untouched. It still records0.5.0(pre-existing drift from the0.6.0.dev0bump in8cfebbc), anduv syncwants to rewrite it, but nothing forces that:uv sync --frozenanduv export --frozen --no-emit-projectboth exit0against the committed lock, which are the two frozen gatesci.ymlactually runs.Verification (local, matching ci.yml pins)
VERSIONresolves to0.5.1from package metadata after reinstalltests/release_readiness_smoke.py: passpython -W error::ResourceWarning -m pytest tests/ -m "not live" --cov-fail-under=86: 1530 passed, 1 deselected, coverage 90.95%ruff check/ruff format --check/bandit -ll/mypy -p bambu_cli: passcheck_layers.py/gen_schemas.py --check(27 schemas) /ci_workflow_smoke/python_compat_smoke/privacy_smoke: passuv sync --frozen/uv export --frozen: exit0withuv.lockunmodified