Repository navigation
chore(deps): pin nexum-runtime at 15e4a38 and videre at 308c734 - #698
Merged
Merged
Conversation
nexum-runtime gained a store format version, schedule (cron) triggers, comment-aware `${NAME}` substitution in the config loader, and three measures: process start time, host delivery latency and block age.
videre followed at 308c734.
This brings shepherd onto both: the ten nexum-runtime pins move to 15e4a38 and the eight videre pins move to 308c734, in the crate manifests, `wit/deps.toml` and `wit/deps.lock`.
The `nexum:host` and videre WIT packages are unchanged between the old revs and the new, so the vendored `wit/deps` tree does not change; only the archive digests do.
The lockfile takes the new revs and two new dependency edges of the runtime (`metrics` and `tracing`); no crate version changes.
No source changes were needed.
AI Assistance: Claude Code used for the re-pin, the WIT pins and the lockfile update.
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
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.
Why
nexum-runtime
mainis15e4a38, and videre followed in nxm-rs/videre#90 (308c734). This brings shepherd onto both, so the engine binary and the image carry the store format version, schedule triggers, the comment-aware config loader, and the three new measures (process start time, host delivery latency, block age).What changed
2085cd2to15e4a38, and the eight videre pins move from9a54866to308c734, in the crate and module manifests.wit/deps.tomlandwit/deps.lockname the same revs, with the new archive digests. The vendoredwit/depstree does not change, because the WIT packages are the same at the old revs and the new.Cargo.locktakes the new revs and two new dependency edges of the runtime (metricsandtracing). No crate version changes.No source changes were needed.
Verification
cargo metadata --lockedpasses, with rustls 0.23.45 and wasmtime 49.0.2.just ciwithCIset passes: fmt, clippy at-D warnings, the orderbook-only gate, rustdoc, both module wasms, nextest (243 passed, and the 1 skipped test is the#[ignore]one) and the doctests. NoSKIP:line.wit-deps updatere-resolves the pins with matching digests and leaves the vendored tree as it is.Merge order
This goes in before #696. The soak runbook in #696 reads
nexum_runtime_start_time_secondsandnexum_runtime_delivery_latency_seconds, which the engine has only from this pin.AI Assistance: Claude Code used for the re-pin, the WIT pins and the lockfile update.