Publish versioned docs runtimes - #4672
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Important Draft PR not reviewedDraft PRs are not automatically reviewed by default.
To automatically review draft PRs, update your CodeRabbit configuration: reviews:
auto_review:
drafts: trueThanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
⏭️ Performance benchmarks were skippedPerf benchmarks (CodSpeed) are opt-in on pull requests — they no longer run on every push. They always run automatically after merge to To run them on this PR, do any of the following, then push a commit (or re-run CI):
|
Binary size checks passed✅ 7 passed
Generated by |
ab3916c to
f6b3757
Compare
e4381e9 to
9de6800
Compare
f6b3757 to
b54b206
Compare
9de6800 to
3fb1257
Compare
|
Closing at the author's request; the docs work will restart from scratch. |
Outcome
Every nightly, canary, and stable BAML release now produces an immutable browser runtime beside its generated standard-library metadata.
The exact stamped release:
bridge_wasmonce in the Web SDK build job;v<version>/runtime.jsonplus content-addressed JavaScript and WASM;docs/versions.json;stdlib.jsonin the version index;Historical index entries without a runtime remain readable for migration, but every newly promoted entry is statically required by the release contract to include one.
End-user impact
This closes the producer half of version-correct runnable docs. A follow-up stack layer will make the TypeScript-only Fumadocs build consume the selected runtime and remove the transitional checked-in snapshot.
Verification
0.18.0runtime packaged successfully and matched the native CLI output for the registered runnable example.