A size budget asserted in CI, and the wasm artifact ships with the release - #684
Merged
Merged
Conversation
onatozmenn
enabled auto-merge (squash)
July 30, 2026 22:24
…lease (#592, #594) [profile.wasm] (root Cargo.toml): opt-level z, one codegen unit, LTO, stripped, panic=abort, for deed-wasm's artifact specifically. Doesn't touch deed's own release profile. Measured: 741,996 bytes uncompressed, 245,645 gzipped (down from 1,084,133 uncompressed on the default release profile). The embedded std/ library is 39,303 of that, about five percent; the rest is the compiler itself. design/04-capabilities.md carries the numbers next to the #590/#591 section they belong with. ci.yml gets a wasm-size job: builds with --profile wasm, fails if the artifact is over 1,500,000 bytes uncompressed or 550,000 gzipped. Room to grow, not slack to stop counting. deed-wasm gets deed_version(), reading env!("CARGO_PKG_VERSION") through the same deed_result_ptr/deed_result_len pair every other verb uses, so the artifact carries its own version rather than trusting a filename (#594). release.yml gets a fourth job building and packaging deed-<tag>-wasm32-unknown-unknown.wasm alongside the three platform binaries, from the same commit and the same tag, and publish now waits on it too.
onatozmenn
force-pushed
the
issue-592-594-wasm-size-and-release
branch
from
July 30, 2026 23:37
e803915 to
1293307
Compare
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.
Closes #592. Closes #594.
[profile.wasm](rootCargo.toml):opt-level = "z", one codegen unit, LTO, stripped,panic = "abort", fordeed-wasm's artifact specifically. Doesn't touchdeed's own release profile.Measured: 741,996 bytes uncompressed, 245,645 gzipped (down from 1,084,133 uncompressed on the default release profile). The embedded
std/library is 39,303 of that, about five percent; the rest is the compiler itself.design/04-capabilities.mdcarries the numbers next to the #590/#591 section they belong with.ci.ymlgets awasm-sizejob: builds with--profile wasm, fails if the artifact is over 1,500,000 bytes uncompressed or 550,000 gzipped. Room to grow, not slack to stop counting.deed-wasmgetsdeed_version(), readingenv!("CARGO_PKG_VERSION")through the samedeed_result_ptr/deed_result_lenpair every other verb uses, so the artifact carries its own version rather than trusting a filename (#594).release.ymlgets a fourth job building and packagingdeed-<tag>-wasm32-unknown-unknown.wasmalongside the three platform binaries, from the same commit and the same tag, andpublishnow waits on it too.Stacked on #683 for the
deed-wasmcrate; will show a clean diff once that merges.