feat: Toolchain Version Bundles for Guaranteed Compatibility #256
Conversation
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
Adds version bundle system for pre-validated, tested tool version combinations: - checksums/toolchain_bundles.json: Bundle definitions with 3 initial bundles: - stable-2025-12: Full toolchain with all 10 tools for all languages - minimal: wasm-tools, wit-bindgen, wasmtime for Rust-only builds - composition: Adds wac, wkg for component composition workflows - toolchains/bundle.bzl: Bundle API for reading/validating bundles: - get_bundle(), get_bundle_tool_version() - validate_bundle(), resolve_tool_versions() - print_bundle_info() for diagnostics - toolchains/extensions.bzl: Module extension tag for bundle configuration: - wasm_tool_repositories.configure(bundle = "stable-2025-12") Each bundle includes: - Tested tool versions with compatibility guarantees - Component model version (0x1000d) and WASI version (preview2) - Tested platform list - Version constraints documenting tool interdependencies Closes #254
This commit completes the Option B (Full Integration) architecture for
toolchain version bundles:
Changes:
- Add get_version_for_tool() and log_bundle_usage() helpers to bundle.bzl
- Add 'bundle' attribute to all 8 toolchain repository rules:
- wasm_toolchain_repository (wasm-tools, wac, wit-bindgen)
- wasmtime_repository
- wizer_toolchain_repository
- wkg_toolchain_repository
- tinygo_toolchain_repository
- wasi_sdk_repository
- cpp_component_toolchain_repository
- jco_toolchain_repository
- Add unified wasm_component_bundle extension to wasm/extensions.bzl
that configures all toolchains from a single bundle parameter
Architecture:
MODULE.bazel
│ wasm_component_bundle.configure(bundle = "stable-2025-12")
▼
Module Extension (wasm/extensions.bzl)
│ Pass bundle to each toolchain repo rule
▼
Repository Rules (each toolchain)
│ Read checksums/toolchain_bundles.json via Label path
│ Extract version for this tool from bundle
▼
Downloaded Tools (with compatible versions)
Each repository rule:
1. Accepts optional 'bundle' attribute
2. If bundle set, reads version from toolchain_bundles.json
3. Falls back to explicit version attribute if not in bundle
4. Logs bundle usage for debugging
This ensures all tools are downloaded with compatible, pre-validated
versions when using a bundle, eliminating version mismatch issues.
Part of #254: Toolchain Version Bundles for Guaranteed Compatibility
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.
Summary
Implements version bundle system for pre-validated, tested tool version combinations (#254).
What's New
checksums/toolchain_bundles.json- Bundle DefinitionsThree initial bundles with December 2025 stable versions:
stable-2025-12minimalcompositionEach bundle includes:
toolchains/bundle.bzl- Bundle APItoolchains/extensions.bzl- Module Extension TagBenefits
Testing
bazel build //test/cpp_binary:hello_cppFuture Work
Closes #254