0.3.65: adopt ciris-server 0.5.202 — the triple (persist v42 / edge v21 / verify v15) - #77
Merged
Merged
Conversation
…ge v21.0.0 / verify v15.0.0)
The pin moves v0.5.200 -> v0.5.201 and, for the first time since 0.3.60, the
substrate moves with it: persist v42.0.0 / edge v21.0.0 / verify v15.0.0
(CIRISServer#559), a MAJOR on both. leviculum unchanged. The lock moves the
server, lens-core, and the substrate crates; one copy of each (cargo tree -i).
What matters to THIS node: persist v42 admits one live `config:` row per
(subject, scope, leaf) and requires a renewal to supersede the row it
replaces (CIRISPersist#814 part 3). The server now keys each config key to
its own leaf `config:{key}:v1`; rows this node wrote before the upgrade on
the legacy `config:v1` leaf still read and are shadowed by version when the
key is next written, so the wizard's keys, `node.alias`, and the retention
knobs survive the restart with no migration step. `registry` / `verify` are
gated co-stewards now; `license` / `grant` join the delegated-duty scopes.
This crate mints no FedCode, so verify v15's `#[non_exhaustive]` changes
nothing here.
clippy -D warnings clean, 114 tests pass, `cargo metadata --locked` proves
the lock (version bumped before the lock refresh, CIRISStatus#75's lesson).
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0132ELwj5JU6t4jEKpwH9bJ7
…r published) v0.5.201's Windows wheel failed on a one-line type break in the server, so its publish never ran; v0.5.202 is the same release plus that cast and a CRLF fix in one gate. Same substrate (persist v42.0.0 / edge v21.0.0 / verify v15.0.0), same 114 tests, clippy clean, `cargo metadata --locked` proves the lock, one copy of each crate. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0132ELwj5JU6t4jEKpwH9bJ7
emooreatx
changed the title
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
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.
The pin moves v0.5.200 -> v0.5.201 and, for the first time since 0.3.60, the
substrate moves with it: persist v42.0.0 / edge v21.0.0 / verify v15.0.0
(CIRISServer#559), a MAJOR on both. leviculum unchanged. The lock moves the
server, lens-core, and the substrate crates; one copy of each (cargo tree -i).
What matters to THIS node: persist v42 admits one live
config:row per(subject, scope, leaf) and requires a renewal to supersede the row it
replaces (CIRISPersist#814 part 3). The server now keys each config key to
its own leaf
config:{key}:v1; rows this node wrote before the upgrade onthe legacy
config:v1leaf still read and are shadowed by version when thekey is next written, so the wizard's keys,
node.alias, and the retentionknobs survive the restart with no migration step.
registry/verifyaregated co-stewards now;
license/grantjoin the delegated-duty scopes.This crate mints no FedCode, so verify v15's
#[non_exhaustive]changesnothing here.
clippy -D warnings clean, 114 tests pass,
cargo metadata --lockedprovesthe lock (version bumped before the lock refresh, CIRISStatus#75's lesson).
🤖 Generated with Claude Code
https://claude.ai/code/session_0132ELwj5JU6t4jEKpwH9bJ7