Skip to content

Layer 2026.09.1: meld 0.53.0, synth 0.61.0, and varve-producer in the layer #128

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
avrabe merged 2 commits into from
Sep 5, 2026
Merged

Layer 2026.09.1: meld 0.53.0, synth 0.61.0, and varve-producer in the layer #128

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
6798feb
Layer 2026.09.1: meld 0.52.0 -> 0.53.0, synth 0.60.0 -> 0.61.0
avrabe Sep 5, 2026
e6f79c9
Layer 2026.09.1: carry varve-producer in the layer
avrabe Sep 5, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 11 additions & 1 deletion .github/workflows/deposit-layer.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -42,7 +42,17 @@ env:
# ordeal rejoined at v0.18.0 — its first cosign-signed release (ordeal#116).
# Entry shape: repo_tool:version[:binary] — binary defaults to the tool
# name; kiln ships its CLI as `kilnd`.
TARBALL_TOOLS: "rivet:v0.35.0 spar:v0.40.0 synth:v0.60.0 witness:v0.43.0 ordeal:v0.19.0 loom:v1.4.1 meld:v0.52.0 kiln:v0.4.4:kilnd"
# varve-producer rides in the layer like any other tool, so a layers
# repository gets a PINNED, signature-verified assembler instead of fetching
# one ad hoc. Its asset is not `<tool>-<version>-<triple>` — the repo is
# `varve` and the binary is `varve-producer` — so the entry spells the binary
# and the template out. `v%V` reconstructs the tag from the bare version
# rather than repeating it, so a bump is one edit and cannot drift.
#
# Bootstrapping is not circular: the deposit downloads the released archive
# exactly as it does for every other tool. The first assembler comes from the
# release; after that a layers repo can pin the one varve signed.
TARBALL_TOOLS: "rivet:v0.35.0 spar:v0.40.0 synth:v0.61.0 witness:v0.43.0 ordeal:v0.19.0 loom:v1.4.1 meld:v0.53.0 kiln:v0.4.4:kilnd pulseengine/varve:v0.32.0:varve-producer:varve-producer-v%V-%T.tar.gz"
WSC_VERSION: v0.11.0
# VS Code extensions carried as kind="vsix" payloads (REQ-VSIX-001).
# Entry shape: repo:version:extension-name:asset-template, where the
Expand Down
Loading