[YuanYuYuan]

Problem

Every version location reads 0.2.0. This PR changes each one to 0.2.1. It changes no code, creates no tag and publishes nothing. It depends on no open pull request.

What changes

file	change	why
Cargo.toml	workspace version and 7 path dependency versions	every crate inherits the version, and cargo publish reads the dependency strings
crates/hiroz/Cargo.toml	hiroz-protocol dependency version	cargo publish reads it
crates/hiroz-msgs/python/	wheel version, __version__	the wheel and the module report 0.2.1
crates/hiroz-py/pyproject.toml	wheel version, hiroz-msgs-py>=0.2.1 bound	the wheel needs the matching message package
crates/hiroz-py/uv.lock	hiroz-py version	the lock was already out of date: its dependency list lacks hiroz-msgs-py, and no script or CI step runs uv
docs/bindings/python.md	example tag v0.2.1	the docs match the release
Cargo.lock	12 workspace entries to 0.2.1, and 5 added hiroz-schema dependency lines	the lock on main was out of date: one entry read 0.1.0, and 5 dependency lists lacked hiroz-schema

hu stays at 0.1.0 in flake.nix, which the version check does not cover. The WIT world stays at hu:plugin@0.1.0, because RELEASING.md says not to bump it with the product version.

The release-version check (scripts/test-release-version-semantics.nu) reads every location above. It fails and names each location that differs from the workspace version. EXPECT_VERSION=0.2.1 also fails when the workspace version is not 0.2.1.

What 0.2.1 contains

git-cliff generates the release notes at tag time. This table lists only the breaking changes since v0.2.0.

pull request	what breaks	who is affected	action
#385	RawSubscriber.inner is no longer public	Rust code with the ffi feature that calls raw.inner.undeclare()	call raw.undeclare()
#375	the QoS history token changes (KeepLast(5) now writes ,5)	tools that compare token strings, and 0.2.0 peers that receive a KeepLast(42) token	upgrade those peers
#275	topic names with an invalid component or an empty component are rejected	callers that pass such names	rename the topic

Raw, C, Go and Python subscribers now join the CPU buffer group by default. Python gets buffer_group='auto'|'cpu'|'off'. A router that allows only the exact topic key starves a joined subscriber, so allow both keys.

After merge

1. Merge this PR.
2. Run the release workflow smoke test: ./scripts/test-release-workflow.nu.
3. When it is green, run git tag v0.2.1 and git push origin v0.2.1.
4. The tag starts release.yml, which builds, smoke-tests, writes the changelog and creates the GitHub Release.

[github-actions]

PR Preview Action v1.8.1
Preview removed because the pull request was closed.
2026-10-24 08:10 UTC

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
see 2 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.