Repository navigation
chore: release 0.6.0 - #154
Merged
Merged
Conversation
Set the version to 0.6.0 and move the Unreleased changelog entries under 0.6.0 (2026-11-06). Refresh the README test and coverage figures to measured values (2,217 tests, 93.5%, 90% floor). Retire plan box D-1 (PR #153 merged) and fold L-3 into L-2.
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
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.
Release PR for 0.6.0, following
docs/releasing.mdstep 1.What changes here
pyproject.toml:0.6.0.dev0→0.6.0.uv.lockwas regenerated to match; besides the project version it adds one dependency marker that the newer uv writes forexceptiongroup.CHANGELOG.md: the[Unreleased]entries move under## [0.6.0] - 2026-11-06, and the compare links are updated. One entry was retitled so the two "sent once" fixes don't read as duplicates. Round 3 stopped retries from republishing a command, and round 4 stopped the MQTT client from resending one when it reconnects.README.md: the badges and the "Tested and hardened" table are updated to measured numbers. The figures were 1,535 tests, 91.1% coverage and an 86% floor. They are now 2,217 tests, 93.5% coverage, and a 90% floor, which is what CI enforces.docs/MASTER-PLAN.md/docs/plan/done.md: D-1 (merge fix: audit round 4 — at-most-once printer commands, pin precedence, heater limits, terminal-safe output #153) is retired. L-3 (verify the 0.5.1 install) is folded into L-2, which verifies 0.6.0 instead.What 0.6.0 ships
Everything since 0.5.1, which is audit rounds 3 and 4:
The full list is in
CHANGELOG.md.Verified locally on this tree
ruff check,ruff format --check,mypy -p bambu_cliandbandit -llpass.ci_workflow_smoke,syntax_smoke,cli_help_smoke,privacy_smokeandpython_compat_smokepass.uv buildproducesplatecli-0.6.0as a wheel and an sdist.package_contents_smokeandtwine checkpass on both.pytest -W error::ResourceWarning -m "not live" --cov-fail-under=90gives 2217 passed and 1 skipped, at 93.53% coverage.plate --versionreportsplate 0.6.0.Not run: the live-printer smoke. Step 5 of
docs/releasing.mdasks for it because this release touches G-code confirm, slice validation and job upload.After merge
git tag v0.6.0 <merge commit> && git push origin v0.6.0. This triggersrelease.yml, which re-runs the CI matrix, builds, publishes to PyPI, and creates the GitHub Release.platecli==0.6.0and'platecli[tui]==0.6.0', then runplate --versionandplate --sim status.0.7.0.dev0.