Date: 2026-07-09 Version: 0.18.0 Coordinator: @w1ne
- Changelog Updated:
CHANGELOG.mdcaptures major changes sincev0.17.10. - Install Docs Updated:
README.mdpinned install examples referencev0.18.0. - Process Docs Reviewed:
RELEASE_PROCESS.mdand release workflow instructions match the tag-triggered automation. - Roadmap Updated:
ROADMAP.mdhas av0.18.0section reflecting what shipped, and stale sections are no longer marked(Current). - Relative Links Checked: Release-facing Markdown links in
README.md,CHANGELOG.md,RELEASE_PROCESS.md,RELEASE_READINESS_CHECKLIST.md, andROADMAP.mdresolve locally.
- Cargo Check:
cargo check --workspacepasses after the workspace version bump. - Tests Passing: Workspace tests were verified in split lanes; the monolithic
cargo test --workspacerun was interrupted by the local environment and is recorded below. - Formatting:
cargo fmt --all -- --checkpasses. - Lints:
cargo clippy --workspace --all-targets -- -D warningspasses. - Diff Hygiene:
git diff --checkreports no whitespace errors.
- Version Bump:
[workspace.package].versionin rootCargo.tomlis0.18.0;Cargo.lockregenerated. - Generated Output Cleanup: No tracked
out/**run artifacts or accidental build products are part of the release-prep diff. - Release Notes Prepared:
CHANGELOG.md0.18.0section is ready to publish as the GitHub release body. - Release Workflow Checked:
.github/workflows/core-release.ymlcreates the release and uploads CLI archives from the pushed tag. - Generated UI Manifest Refreshed:
packages/ui/src/peripherals/manifest.jsonin the parent repo was regenerated from the v0.18.0 CLI.
- Working Tree Reviewed: Release-prep diff contains expected metadata, documentation, lint fixes, one test-harness fix, and generated lockfile changes.
- Release Notes Reviewed: GitHub release body should use the
CHANGELOG.md0.18.0section. - Release Branch Ready: Release prep is committed on
release/v0.18.0and ready for PR review. - CI Green: Pushed release branch passes GitHub Actions.
- Release Tagged:
v0.18.0tag is created and pushed only after review/CI.
Status: [x] LOCAL RELEASE PREP COMPLETE; [ ] READY TO TAG
- Full release confidence still depends on the CI matrix for hardware-backed and toolchain-specific lanes that are not practical to reproduce in this local checkout.
- A monolithic
cargo test --workspacerun reached the long e-paper E2E path and was terminated by the local environment. The suite was then verified in split lanes:cargo test -p labwired-core --test intmatrix_alarm- focused core continuation lanes through
xtensa_regs cargo test -p labwired-cli --test breakpointscargo test --workspace --exclude labwired-core --exclude labwired-cli --exclude labwired-dap --exclude labwired-gdbstubcargo test -p labwired-dap --test e2eafter buildingfirmware-ci-fixturecargo test -p labwired-gdbstub --test gdb_e2eoutside the sandbox because the test binds a local TCP port.