Repository navigation
chore(varve): put retired-roots back under [realm.pulseengine] - #1218
Merged
Merged
Conversation
avrabe
enabled auto-merge
November 10, 2026 18:33
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
#1161 inserted the [realm.pulseengine-wasm] block between gale's [realm.pulseengine] keys and its retired-roots entry, so TOML attached retired-roots (the retired pulseengine root 4e771dc6, last layer 2026.09.1) to pulseengine-wasm. A consumer pinned to an old pulseengine layer then got "No valid signatures" instead of the retired-root diagnostic. Found by the spar session. The pulseengine-wasm block now follows retired-roots. Parsed with tomllib: pulseengine = registry, retired-roots, trust-root; pulseengine-wasm and covalent = registry, trust-root; the pulseengine table equals gale's. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_015HMQUV3u86jN2hmCtXNTc9
avrabe
force-pushed
the
chore/varve-realms-retired-roots
branch
from
November 10, 2026 22:49
8ea6e0e to
4c8c06a
Compare
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.
retired-roots(the retired pulseengine root4e771dc6…, last layer 2026.09.1) had ended up under[realm.pulseengine-wasm]. #1161 inserted that realm block between gale's[realm.pulseengine]keys and itsretired-rootsentry, so TOML attached the key to the wrong table. A consumer pinned to an old pulseengine layer got "No valid signatures" instead of the retired-root diagnostic. The spar session found it.The fix moves the
pulseengine-wasmblock belowretired-roots; no content changes.Check (
tomllib):pulseenginepulseengine-wasmcovalentvarve verifycan't confirm it on this machine yet: the installed varve 0.32.0 rejectsretired-rootsitself. spar#613 and pulseengine.eu#365 copied this file and will re-copy it.🤖 Generated with Claude Code
https://claude.ai/code/session_015HMQUV3u86jN2hmCtXNTc9