chore: release v0.6.0

[aprilnea]

🤖 New release

• openlogi-core: 0.5.3 -> 0.5.4
• openlogi-hidpp: 0.5.3 -> 0.5.4
• openlogi-hid: 0.5.3 -> 0.5.4
• openlogi-assets: 0.5.3 -> 0.5.4
• openlogi-cli: 0.5.3 -> 0.5.4
• openlogi-hook: 0.5.3 -> 0.5.4
• openlogi: 0.5.3 -> 0.5.4

Changelog

openlogi-core

0.5.4 - 2026-06-07

Added

• (agent) tarpc IPC server backed by the orchestrator + device I/O
• (agent) define tarpc IPC service contract + serde-derive wire types

Fixed

• (agent) give the agent its own single-instance lock

Other

• Merge origin/master into feat/agent-daemon-split

openlogi-hidpp

0.5.4 - 2026-06-07

Added

• (agent) tarpc IPC server backed by the orchestrator + device I/O
• (agent) define tarpc IPC service contract + serde-derive wire types

Fixed

• (agent) give the agent its own single-instance lock

Other

• Merge origin/master into feat/agent-daemon-split

openlogi-hid

0.5.4 - 2026-06-07

Added

• (agent) tarpc IPC server backed by the orchestrator + device I/O
• (agent) define tarpc IPC service contract + serde-derive wire types

Fixed

• (agent) give the agent its own single-instance lock

Other

• Merge origin/master into feat/agent-daemon-split

openlogi-assets

0.5.4 - 2026-06-07

Added

• (agent) tarpc IPC server backed by the orchestrator + device I/O
• (agent) define tarpc IPC service contract + serde-derive wire types

Fixed

• (agent) give the agent its own single-instance lock

Other

• Merge origin/master into feat/agent-daemon-split

openlogi-cli

0.5.4 - 2026-06-07

Added

• (agent) tarpc IPC server backed by the orchestrator + device I/O
• (agent) define tarpc IPC service contract + serde-derive wire types

Fixed

• (agent) give the agent its own single-instance lock

Other

• Merge origin/master into feat/agent-daemon-split

openlogi-hook

0.5.4 - 2026-06-07

Added

• (agent) tarpc IPC server backed by the orchestrator + device I/O
• (agent) define tarpc IPC service contract + serde-derive wire types

Fixed

• (agent) give the agent its own single-instance lock

Other

• Merge origin/master into feat/agent-daemon-split

openlogi

0.5.4 - 2026-06-07

Added

• (agent) tarpc IPC server backed by the orchestrator + device I/O
• (agent) define tarpc IPC service contract + serde-derive wire types

Fixed

• (agent) give the agent its own single-instance lock

Other

• Merge origin/master into feat/agent-daemon-split

---

This PR was generated with release-plz.

[greptile-apps]

Greptile Summary

This is an automated release PR generated by release-plz, intended to bump all workspace crates from 0.5.3 to a new version. However, the PR title and description claim the target version is 0.5.4, while every changed file (Cargo.toml, Cargo.lock, all crate manifests, and CHANGELOG.md) actually reflects a bump to 0.6.0.

• All workspace crate versions in Cargo.toml, Cargo.lock, and individual crate manifests are updated from 0.5.3 → 0.6.0, not 0.5.4 as the PR title claims.
• CHANGELOG.md adds a new entry under 0.6.0, consistent with the file changes but inconsistent with the PR description.
• The changelog covers three items: a new tarpc IPC server backed by the orchestrator, a new IPC service contract with serde wire types, and a fix for single-instance locking in the agent.

Confidence Score: 4/5

The file changes are internally consistent (all crates move to 0.6.0), but the PR title and description incorrectly label this as a 0.5.4 patch release.

Every changed file consistently bumps to 0.6.0, yet the PR metadata advertises 0.5.4. If merged as-is, release tooling, tags, and downstream semver consumers will see a minor version bump under a patch release label, which can cause confusion about compatibility guarantees.

Cargo.toml and CHANGELOG.md — both confirm the actual release is 0.6.0, directly contradicting the PR title and description.

Important Files Changed

Filename	Overview
CHANGELOG.md	New changelog entry added for version 0.6.0, but PR description claims 0.5.4 — the entry version and PR metadata are inconsistent.
Cargo.toml	Workspace version and openlogi-cli/hidpp dependency versions bumped from 0.5.3 to 0.6.0, contradicting the PR's claimed 0.5.4 release.
Cargo.lock	All workspace crates (openlogi, openlogi-agent, openlogi-core, etc.) and xtask updated from 0.5.3 to 0.6.0 consistently with Cargo.toml changes.
crates/openlogi-cli/Cargo.toml	Intra-workspace dependency versions for openlogi-core, openlogi-hid, and openlogi-assets bumped to 0.6.0.
crates/openlogi-hid/Cargo.toml	openlogi-core dependency bumped to 0.6.0.
crates/openlogi-hook/Cargo.toml	openlogi-core dependency bumped to 0.6.0.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[release-plz bot] -->|generates PR titled v0.5.4| B[PR #164]
    B --> C{Actual file changes}
    C -->|Cargo.toml workspace.package.version| D[0.5.3 → 0.6.0]
    C -->|Cargo.lock all crates| E[0.5.3 → 0.6.0]
    C -->|crates/* Cargo.toml deps| F[0.5.3 → 0.6.0]
    C -->|CHANGELOG.md new entry| G[0.6.0 entry added]
    D & E & F & G -->|version in files| H[0.6.0]
    B -->|PR title/description claims| I[v0.5.4]
    H -->|mismatch| I

Loading

_{Reviews (3): Last reviewed commit: "chore: release v0.6.0" | Re-trigger Greptile}

[greptile-apps]

Version mismatch: PR claims 0.5.4 but files bump to 0.6.0

The PR title ("release v0.5.4") and description list all packages as going from 0.5.3 → 0.5.4, but every changed file (Cargo.toml, Cargo.lock, crates/openlogi-cli/Cargo.toml, crates/openlogi-hid/Cargo.toml, crates/openlogi-hook/Cargo.toml) and the CHANGELOG.md entry all reflect a 0.5.3 → 0.6.0 bump. This is a minor-version bump according to semver, not a patch release. Merging this with a misleading title risks downstream consumers expecting a patch-compatible release but receiving a potentially breaking minor update. The PR metadata should be corrected to match the actual released version (v0.6.0) before merging.