Repository navigation
Move the varve pin to covalent rolling 2026.11.16 (loom 1.5.4) - #245
Merged
Merged
Conversation
2026.11.16 composes pulseengine 2026.11.25, which carries loom 1.5.4, and pulseengine-wasm 2026.11.4. Every other pinned tool keeps the version it had in 2026.11.15. The layer's signed-index entry (covalent-layers #98) is not merged yet; varve installs it at counter 17 and reports, without enforcing, that the index's newest is 16. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01KEjmjaju7y4RBwmiuZ7Eem
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.
Follow-up to #238. Moves
varve.tomlfrom covalent/rolling2026.11.15to2026.11.16, the covalent layer that carries loom 1.5.4 (deposited 2026-11-19 08:10Z from covalent-layers #97).2026.11.16 composes pulseengine
2026.11.25and pulseengine-wasm2026.11.4. Only loom changes: 1.5.3 → 1.5.4. The other 13 tools keep their 2026.11.15 versions (rivet 0.42.2, spar 0.49.0, meld 0.69.0, synth 0.90.0, witness 0.46.0, ordeal 0.37.0, kiln 0.7.3, wsc 0.12.1, wasm-tools 1.263.0, wac 0.12.0, wasmtime 50.0.2, wit-bindgen 0.63.0, wkg 0.16.2).Checked on the mini:
varve install: exit 0, layersha256:a38d3e34…at index counter 17.varve which <tool>names2026.11.16for all 14 tools;loom --versionprintsloom 1.5.4.varve verify: signature OK, composed layers verified against their realms (pulseengine 19 tools, pulseengine-wasm 7). It exits 1 only on two PATH shadows local to that machine (~/.local/bin/warte,~/.local/bin/with-device), same as on Pin the toolchain through varve: covalent realm, rolling 2026.11.15 #238.rivet validate:Result: PASS (200 warnings), exit 0.Signed index not merged yet: the layer's signed-index entry is covalent-layers #98, which waits on the owner. Until it merges, the index's newest is counter 16, and
varve installsays so but installs 2026.11.16 anyway ("reported, not enforced"). The layer and both composed layers verify against their realms' trust roots either way.varve outdatedlists 2026.11.16 as newest only after #98.CI here does not run varve, so this PR's checks don't exercise the pin.
🤖 Generated with Claude Code
https://claude.ai/code/session_01KEjmjaju7y4RBwmiuZ7Eem