chore: bump workspace version for publish (0.4.0 -> 0.5.0)#971
Draft
ohdearquant wants to merge 6 commits into
Draft
chore: bump workspace version for publish (0.4.0 -> 0.5.0)#971ohdearquant wants to merge 6 commits into
ohdearquant wants to merge 6 commits into
Conversation
Bump workspace.package.version 0.4.0 -> 0.5.0 and all internal path-dependency version pins to match. Every workspace crate already has a 0.4.0 release live on crates.io (published 2026-07-12), and khive-pack-comm's published 0.4.0 predates fix(pack-comm) #914 (namespace-scoped health/probe, merged 2026-07-13) that already landed on main at the same version number. 0.5.0 is the first version strictly greater than every published version of any workspace crate, so the next scripts/publish.sh run supersedes everything currently on the index. No code changes. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
…ky tx-age sweep run_writer_task registers a writer_task_tx handle in the process-wide tx_registry singleton; the checkpoint tx_age_sweep_* tests read that singleton under #[serial(tx_registry)]. The writer_task.rs tests that spawn a writer task were missing from the group, leaking a longer-lived writer_task_tx into the sweep's oldest() read and intermittently failing the assertion on main CI. Join them to the serial group. No prod change.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
workspace.package.version0.4.0 -> 0.5.0 and every internal path-dependency version pin (37Cargo.tomlfiles) to match. No code changes.max_version: "0.4.0").khive-pack-comm's published 0.4.0 (https://crates.io/api/v1/crates/khive-pack-comm) predatesfix(pack-comm): health and probe honor the injected namespace (#914)(8cebf3a, landed 2026-07-13T00:32Z on main) — main carries fixes crates.io does not, at the same version number. 0.5.0 is the first version strictly greater than every published version of any workspace crate, so the nextscripts/publish.shrun supersedes everything currently on the index.This unblocks the crates.io publish chain and, downstream, khive-cloud#161 — the cloud pin bump for
khive-pack-commpast its stale-0.3.0 pin (that issue explicitly names "a new khive-pack-comm crates.io release cut from upstream main (post upstream PR #914)" as the blocker).Test plan
cargo check --workspace(fromcrates/) — passes clean at 0.5.0cargo publish -p khive-types --dry-run --allow-dirty(fromcrates/) — packages, verifies, and compiles v0.5.0 successfully (upload aborted only because it's a dry run)scripts/publish.sh(preflight, then--live) once this PR merges🤖 Generated with Claude Code