Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: calculate SRI for WASM file after running wasm-opt #665

Merged
merged 1 commit into from
Jan 8, 2024

Conversation

ctron
Copy link
Collaborator

@ctron ctron commented Jan 8, 2024

In case wasm-opt is enabled (by default it is not) the SRI digest must be built from the final WASM file, after running wasm-opt. Otherwise the digest won't match.

Closes: #660

In case wasm-opt is enabled (by default it is not) the SRI digest must
be built from the final WASM file, after running wasm-opt. Otherwise
the digest won't match.

Closes: trunk-rs#660
@ctron ctron added this to the 0.18.4 milestone Jan 8, 2024
@ctron ctron added the bug Something isn't working label Jan 8, 2024
@ctron ctron merged commit 0da94db into trunk-rs:main Jan 8, 2024
5 checks passed
@ctron ctron deleted the feature/fix_660_1 branch January 8, 2024 09:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Integrity hash is incorrect when wasm-opt is enabled
1 participant