Skip to content

Move the varve pin to covalent rolling 2026.11.16 (loom 1.5.4) - #245

Merged
avrabe merged 1 commit into
mainfrom
chore/varve-pin-2026.11.16
Nov 19, 2026
Merged

avrabe merged 1 commit into
mainfrom
chore/varve-pin-2026.11.16

Conversation

@avrabe

@avrabe avrabe commented Nov 19, 2026

Copy link
Copy Markdown
Contributor

Follow-up to #238. Moves varve.toml from covalent/rolling 2026.11.15 to 2026.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.25 and pulseengine-wasm 2026.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, layer sha256:a38d3e34… at index counter 17.
  • varve which <tool> names 2026.11.16 for all 14 tools; loom --version prints loom 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 install says 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 outdated lists 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

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
@avrabe
avrabe merged commit 2f50579 into main Nov 19, 2026
12 checks passed
@avrabe
avrabe deleted the chore/varve-pin-2026.11.16 branch November 19, 2026 09:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant