Repository navigation
Conversation
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
This branch has not been deployed
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.
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 were falling back to unpinned~/.cargo/bincopies. That has been the case since the 2026-11-13 PATH fix put the shims first; smithy coordinated the change with the owner.varve.toml: realmcovalent, channelrolling, layer2026.11.10. That layer composes pulseengine2026.11.18and the pulseengine-wasm layer, so one pin covers both tool sets.varve-realms.toml: the canonical realm file from the varve v0.47.0 release, plus thecovalentrealm as published in pulseengine/covalent-layers.Tool versions this pin runs (
<tool> --versionthrough the shims): rivet 0.41.1, spar 0.49.0, loom 1.5.2, meld 0.68.0, synth 0.90.0, witness 0.46.0, wasm-tools 1.263.0, wac 0.12.0, wasmtime 50.0.1, wit-bindgen 0.63.0, wkg 0.16.1, ordeal 0.36.1, kiln 0.7.2, wsc 0.12.0.Review point: these are CURRENT versions. If this repo's gates were run with older ones (e.g. a
~/.cargo/binrivet 0.38.0), results can differ. An older layer cannot be pinned instead: on a machine that has installed a newer layer of the same line, varve refuses it as a rollback (pulseengine/varve#256).Checked on the mini:
varve installverified the layer and its two composed layers against their realms' roots.varve verifypasses apart from one known shadow,~/.local/bin/with-device, which is kept on purpose.varve whichnames2026.11.10for every tool listed above.Nothing else changes. CI here does not run varve unless a workflow already did.
rivet validate under this pin (rivet 0.41.1), on main at dc1e603: Result: PASS (199 warnings)
🤖 Generated with Claude Code
https://claude.ai/code/session_01KEjmjczUmt6Rdd9DRKe75Z