chore: release v0.8.11

[AprilNEA]

Second attempt to finish the interrupted v0.8.11 release; replaces #1643, which merged as f3c19020 but was skipped by release-plz with skipping release: current commit is not from a release PR. With release_always = false, release-plz looks up the pull requests GitHub associates with the merge commit and releases only when one of them has a release-plz/ head branch (release_plz_core::command::release::should_release). #1643 came from chore/release-v0.8.11-recovery, so nothing was published and no tag was cut. #874 recovered v0.7.10 from release-plz/recovery-v0.7.10; this PR follows that branch name.

State on crates.io: openlogi-assets, openlogi-device-registry, openlogi-camera, openlogi-core, openlogi-hidpp-derive are at 0.8.11 from the first attempt; the other eight crates are at 0.8.10 and v0.8.11 does not exist. Master f3c19020 already carries the 1.99 lint fix (#1638) and the 0.8.11 changelog (#1643).

Change: the release_always comment in release-plz.toml said to re-run the failed job on the same SHA. That is right only when credentials failed; when the tree itself cannot publish, the re-run fails again. The comment now names both cases and the branch-prefix requirement this PR had to learn.

Merge with the subject chore: release v0.8.11 (#<this PR>): cargo xtask release checkout-version-bump selects the newest commit with that subject, release-plz finds this release-plz/ PR on it, skips the five crates already on the registry, publishes the remaining eight, and cuts v0.8.11 on the merge commit; release.yml then builds the installers.

Testing

• cargo xtask release check-publish on master 064c520a (same Rust tree): publish closure valid, 14 publishable packages.
• Comment-only change to release-plz.toml; check toml runs in the commit hook. No Rust gate applies.

[greptile-apps]

Confidence Score: 5/5

[Low risk] Updates release automation documentation.

The PR appears safe to merge; no actionable issue was identified in the comment-only change.

Summary

This PR clarifies the release-recovery guidance in release-plz.toml, distinguishing a retry after credential or network failure from a new release PR after a tree-level publishing failure.

_{Reviews (1) · Last reviewed commit: "chore: release v0.8.11"}