aot: carry standalone runtime link metadata#59
Merged
dank-openai merged 1 commit intoMay 20, 2026
Conversation
bfc008b to
7060d35
Compare
f3011e4 to
1b2b4fe
Compare
dank-openai
added a commit
that referenced
this pull request
May 18, 2026
# Problem Solved Consumers need a normal bundle surface for the XLS-owned standalone AOT runtime archive after it is released. They should not need to rediscover native artifact filenames or special-case local validation paths. # What Changed - Teach bundle materialization and download logic about the optional standalone runtime archive. - Export the archive through generated runtime repos and artifact config when a bundle publishes it. - Keep older non-AOT release bundles usable when they do not contain the new archive. - Add self-tests covering artifact resolution and generated runtime exports. # Validation - Existing `rules_xlsynth` self-tests passed for the updated runtime bundle surface. - The design was validated in downstream carrier proofs on macOS and Ubuntu 24.04 with bundles that expose the archive to real AOT consumers. # Landing Order Depends on xlsynth/xlsynth#8. This is the bundle-contract handoff between the XLS producer artifact and downstream public and private consumers. <!-- spr-stack:start --> **Stack**: - #59 - ➡ #58⚠️ *Part of a stack created by [spr-multicommit](https://github.com/mattskl-openai/spr-multicommit). Do not merge manually using the UI - doing so may have unexpected results.* <!-- spr-stack:end -->
Materialize the runtime link manifest with the archive and keep the generated artifact config pair self-contained for downstream consumers. branch:dank-spr/rules-xlsynth-aot-runtime-link-metadata
7060d35 to
d65666b
Compare
meheff
approved these changes
May 19, 2026
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.
Before this change, a runtime bundle could effectively say:
After this change, the bundle says:
Concretely, the generated runtime repo now exports:
@<name>_runtime//:xls_aot_runtime@<name>_runtime//:xls_aot_runtime_file@<name>_runtime//:xls_aot_runtime_link_config_fileand the generated
xlsynth_artifact_config.tomlrecords both:The producer-owned TOML currently looks like this conceptually:
Stack: