Fix duplicate-key error in wasm target compilation check#593
Draft
Copilot wants to merge 1 commit into
Conversation
Copilot created this pull request from a session on behalf of
anweiss
June 15, 2026 18:41
View session
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.
The
Compilation check for wasm target (stable)job failed with a TOMLduplicate keyerror becausemainalready defines[package.metadata.wasm-pack.profile.release], and this branch added a second copy — so the PR-merge tree contained the key twice, abortingcargo checkbefore compilation.Changes
Cargo.toml: Remove the redundant[package.metadata.wasm-pack.profile.release]block added by this branch. The equivalentwasm-opt = falsesetting inherited frommainis preserved, so wasm-opt stays disabled for wasm-pack builds.