Skip to content

Pin the toolchain through varve: covalent realm, rolling 2026.11.15 - #238

Merged
avrabe merged 2 commits into
mainfrom
chore/varve-realm-pin
Nov 19, 2026
Merged

avrabe merged 2 commits into
mainfrom
chore/varve-realm-pin

Conversation

@avrabe

@avrabe avrabe commented Nov 13, 2026 •

Copy link
Copy Markdown
Contributor

Adds a varve toolchain pin, so the ~/.varve/shims (first on PATH on the org's machines) resolve in this repository. Without a pin they refuse, and sessions here fall back to unpinned ~/.cargo/bin copies.

  • varve.toml: realm covalent, channel rolling, layer 2026.11.15. It is the newest covalent layer in the realm's signed index (counter 16). It composes pulseengine 2026.11.23 and pulseengine-wasm 2026.11.4, so one pin covers both tool sets.
  • varve-realms.toml: the canonical realm file from the varve v0.47.0 release, plus the covalent realm as published in pulseengine/covalent-layers.

Updated 2026-11-19 from 2026.11.10 and rebased onto main (1ded182). The layer with loom 1.5.4 is not deposited yet (covalent-layers #97). A follow-up bumps the pin once it is.

Tool versions this pin runs (varve which <tool> names layer 2026.11.15 for each; versions from <tool> --version through the shims): rivet 0.42.2, spar 0.49.0, loom 1.5.3, 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 accepted the layer at index counter 16. varve verify checks the signature and the digests of both composed layers (18 + 7 tools match). It exits 1 only on two PATH shadows local to that machine, ~/.local/bin/with-device and ~/.local/bin/warte, which have nothing to do with this repo.

rivet validate under this pin (rivet 0.42.2): Result: PASS (200 warnings), exit 0.

Nothing else changes. CI here does not run varve.

🤖 Generated with Claude Code

https://claude.ai/code/session_01KEjmjaju7y4RBwmiuZ7Eem

avrabe and others added 2 commits November 19, 2026 07:17
varve.toml pins the covalent layer 2026.11.10, which composes pulseengine
2026.11.18 and pulseengine-wasm. varve-realms.toml carries the realms'
registries and trust roots, so the shims on PATH resolve here without an
environment variable.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01KEjmjczUmt6Rdd9DRKe75Z
2026.11.15 is the newest covalent layer in the realm's signed index
(counter 16). It composes pulseengine 2026.11.23 (loom 1.5.3) and
pulseengine-wasm 2026.11.4. The layer with loom 1.5.4 is not deposited
yet (covalent-layers #97).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01KEjmjaju7y4RBwmiuZ7Eem
@avrabe
avrabe force-pushed the chore/varve-realm-pin branch from 7189d93 to cecc6e1 Compare November 19, 2026 06:18
@avrabe avrabe changed the title Pin the toolchain through varve: covalent realm, rolling 2026.11.10 Pin the toolchain through varve: covalent realm, rolling 2026.11.15 Nov 19, 2026
@avrabe
avrabe merged commit 12207f2 into main Nov 19, 2026
12 checks passed
@avrabe
avrabe deleted the chore/varve-realm-pin branch November 19, 2026 07:17
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