Re-pin wkg.lock automatically when publishing the bridge wasm - #164
Merged
Conversation
Rust is not byte-reproducible across toolchains, so every publish yields a new digest even when the source is unchanged: the run that verified GHCR permissions rebuilt the wasm 1.4KB smaller and broke main and every open PR with a digest mismatch, needing a manual lock refresh (bytecodealliance#163). The workflow now re-pins the lock and pushes it back in the same run, so publishing and pinning land together. It builds before committing, so a wasm that does not build is never pinned.
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.
Rust is not byte-reproducible across toolchains, so every publish yields a new digest even when the source is unchanged: the run that verified GHCR permissions rebuilt the wasm 1.4KB smaller and broke main and every open PR with a digest mismatch, needing a manual lock refresh (#163).
The workflow now re-pins the lock and pushes it back in the same run, so publishing and pinning land together. It builds before committing, so a wasm that does not build is never pinned.