chore: bump main to 0.6.0.dev0 - #135
Merged
Merged
Conversation
Step 6 of docs/releasing.md, after v0.5.1 was tagged and published. Without it main keeps claiming to be the released version: anyone running from a source checkout reports `plate 0.5.1` while executing unreleased code, and the bug-report template asks for exactly that string. This step was missed after 0.3.0, which is why main spent a day identifying as 0.3.0 while seven commits ahead of the tag. CHANGELOG is untouched — `## [Unreleased]` is already an empty heading and the compare link already points at v0.5.1...HEAD.
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 6 of docs/releasing.md, now that
v0.5.1is tagged and published. One line.maincarries a.devNsuffix between releases so a source build is never mistaken for the released wheel of the same number. Right nowmainsits at a bare0.5.1, so anyone running from a source checkout reportsplate 0.5.1while executing unreleased code — and the bug-report template asks for exactly that string. The doc calls this out as having been missed after 0.3.0, whenmainspent a day identifying as0.3.0while seven commits ahead of the tag.What
pyproject.toml:version = "0.5.1"→"0.6.0.dev0". Single source of truth;bambu_cli.constants.VERSIONresolves from package metadata.CHANGELOG.mdis untouched:## [Unreleased]is already an empty heading and[Unreleased]already compares fromv0.5.1...HEAD.uv.lockis untouched, consistent with the 0.5.1 release PR. Note it still recordsplatecli 0.5.0— pre-existing drift, now two releases stale.uv sync --frozenanduv export --frozen --no-emit-projectboth exit0against it, so nothing inci.ymlforces it; worth a separate cleanup PR rather than smuggling a lock churn into a version bump.Verification (local, matching ci.yml pins)
VERSIONresolves to0.6.0.dev0from 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/check_layers.py: passuv sync --frozen/uv export --frozen: exit0withuv.lockunmodified