chore: release v0.3.0#18
Conversation
There was a problem hiding this comment.
✅ No new issues found.
Reviewed changes — release-plz auto-generated patch release bumping the workspace from 0.2.0 to 0.2.1 to ship the stall-guard fix landed in 4a97fa4.
- Workspace version bump —
workspace.package.versionflips to0.2.1inCargo.toml, and the matchingversion = "0.2.1"strings on path dependencies in the root manifest and inopenlogi-cli,openlogi-hid, andopenlogi-hookare updated consistently. Cargo.lockregenerated — every workspace crate (including the unpublishedopenlogi-gui, which inherits the workspace version) moves to0.2.1.CHANGELOG.mdentry — adds the## [0.2.1]block under the rootopenlogichangelog with therelease-plzstall-guard fix under### Other, matching the config where only the root crate emits a tag and Release.
Unified versioning, lockfile, and changelog are all in sync; nothing actionable to flag.
Claude Opus | 𝕏
c977bc2 to
8180856
Compare
There was a problem hiding this comment.
✅ No new issues found.
Reviewed changes — release-plz force-pushed the 0.2.1 release on top of merged PR #28, swapping which fix this release ships.
- CHANGELOG entry rewritten — the
## [0.2.1]block under### Fixednow references*(openlogi-hid)* enumerate Bluetooth-LE-direct HID++ mice (Lift, Signature) (#28)instead of the previously-shown release-plz stall-guard CI commit. The compare link is keyed toopenlogi-hid-v0.2.0...openlogi-hid-v0.2.1, so release-plz only captures commits touching theopenlogi-hidcrate —4a97fa4(CI) andd747bb5(settings) intentionally don't appear. - Release date rolled —
2026-05-31→2026-06-01, regenerated after the rebase across the day boundary. - Version bumps unchanged — workspace + path-dep
version = "0.2.1"strings andCargo.lockentries (including the unpublishedopenlogi-guiinheriting from the workspace) remain consistent with the previous review.
Mechanical release-plz delta; the new commits are coherent with the swap in shipped fix.
Claude Opus | 𝕏
8180856 to
b9da76a
Compare
b9da76a to
87a98da
Compare
There was a problem hiding this comment.
✅ No new issues found.
Reviewed changes — release-plz force-pushed a brand-new 0.3.0 release that supersedes the previously-pending 0.2.1 release entirely; the diff is now keyed against master at 0.2.0.
- Workspace version bump —
workspace.package.versionflips to0.3.0inCargo.toml, and the matchingversion = "0.3.0"strings on path dependencies in the root manifest and inopenlogi-cli,openlogi-hid, andopenlogi-hookare updated consistently. Cargo.lockregenerated — every workspace crate (including the unpublishedopenlogi-gui, which inherits the workspace version) moves to0.3.0.CHANGELOG.mdentry — adds the## [0.3.0]block under the rootopenlogichangelog with*(openlogi-gui)* add Russian localization and language select (#38)under### Addedand*(gui)* stabilize device tab ordering (#37)under### Fixed. Release date2026-06-01.- Minor bump justified — the PR body surfaces cargo-semver-checks output flagging
openlogi-core::DeviceModelInfofor a newserial_numberfield and droppedCopyderive. Selecting 0.3.0 (rather than a patch) is the correct pre-1.0 convention for breaking changes.
Version strings, lockfile, and changelog entry are mutually consistent; nothing actionable to flag.
Claude Opus | 𝕏

🤖 New release
openlogi-core: 0.2.0 -> 0.3.0 (⚠ API breaking changes)openlogi-hid: 0.2.0 -> 0.3.0 (✓ API compatible changes)openlogi-assets: 0.2.0 -> 0.3.0openlogi-cli: 0.2.0 -> 0.3.0 (✓ API compatible changes)openlogi-hook: 0.2.0 -> 0.3.0openlogi: 0.2.0 -> 0.3.0⚠
openlogi-corebreaking changesChangelog
openlogi-coreopenlogi-hidopenlogi-assetsopenlogi-cliopenlogi-hookopenlogiThis PR was generated with release-plz.