chore(checksum_updater): manage wsc; bump signing tool 0.9.0 → 0.9.2#524
Merged
Conversation
The updater previously skipped wsc (github_repo pulseengine/sigil) because early releases were dual-natured (per-OS CLI binaries + a wasm-CLI module wsc-cli.wasm). wsc-cli.wasm was capped at v0.7.0; from v0.9.x the registry uses only per-OS native binaries, so wsc fits the existing PerPlatformAsset pattern (version-less asset names; mixed extension: bare unix binaries vs `.exe` on Windows). Closes the #498 updater tail — every tracked tool is now auto-managed. Verified: `update --tools wsc` detects v0.9.2 and resolves all 5 platforms; `validate --tools wsc` re-downloads and confirms 5/5 checksums; linux_amd64 sha256 cross-checked against upstream's published wsc-linux-x86_64.sha256. NOTE (signing-path): bumping latest_version 0.9.0 -> 0.9.2 advances the wsc signing toolchain (resolved from this file via MODULE.bazel). Asset format is unchanged from the working 0.9.0 (same native-binary pattern), but this is a signing-path change — run a signing build_test and review before merge. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
avrabe
added a commit
that referenced
this pull request
Jun 18, 2026
…#525) CONTRIBUTING had no mention of the checksum_updater, so contributors hand-edited checksums and pins drifted silently — the original motivation for #498. Add an "Updating Tool Versions" section: the JSON registry is the source of truth (latest_version is the pin; no separate MODULE.bazel pin for managed tools), the update/validate/dry-run commands, the UrlPattern taxonomy (StandardTarball/SingleBinary, PerPlatformAsset, UniversalWasm+AssetExists), how to register a new tool, and a signing-path caveat for wsc. Closes the #498 documentation item (item 5). Items 1-2 (universal-wasm pattern + asset-existence filter) shipped in #502; item 4 (wsc PerPlatformAsset + 0.9.2 bump) in #524. Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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
1 participant
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.
What
Wires wsc (
pulseengine/sigil, the signing tool) into the checksum_updater and bumps it 0.9.0 → 0.9.2.The updater previously skipped wsc (commented out, tracked as the #498 tail) because early releases were dual-natured — per-OS CLI binaries plus a wasm-CLI module
wsc-cli.wasm.wsc-cli.wasmwas capped at v0.7.0; from v0.9.x the registry uses only per-OS native binaries, so wsc fits the existingPerPlatformAssetpattern (version-less asset names; mixed extension — bare unix binaries vs.exeon Windows). With this, every tracked tool is auto-managed — closes the #498 updater tail.Verification (evidence)
update --tools wsc --dry-run→ detectspulseengine/sigil v0.9.2, resolves all 5 platform assets (byte sizes match the GitHub asset list), classifies patch.update --tools wsc→ writes the 0.9.2 registry block + bumpslatest_version.validate --tools wsc→ re-downloads all 5 assets, 5/5 checksums valid.linux_amd64sha256 cross-checked against upstream's publishedwsc-linux-x86_64.sha256→ exact match.descriptionfield the updater's serializer dropped (cosmetic; nothing reads it — toolchains hardcode_SUPPORTED_PLATFORMS).Bumping
latest_version0.9.0 → 0.9.2 advances the wsc signing toolchain (resolved fromchecksums/tools/wsc.jsonviaMODULE.bazel). The asset format is unchanged from the already-working 0.9.0 (identical native-binary pattern, no wasm involved), so the 0.7.0-style "fetches but can't run" risk is low — but this is still a signing-path change. Please run a signing build_test and review before merge. If you'd rather land the updater wiring without moving the signing tool yet, I can split thewsc.jsonbump into a separate PR.🤖 Generated with Claude Code