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

v2.3.0 #95

Merged
merged 1 commit into from
Dec 8, 2024
Merged

v2.3.0 #95

merged 1 commit into from
Dec 8, 2024

Conversation

notgull
Copy link
Member

@notgull notgull commented Dec 3, 2024

@taiki-e
Copy link
Collaborator

taiki-e commented Dec 4, 2024

LGTM aside from CI failure (due to rustwasm/wasm-bindgen#4304).

Signed-off-by: John Nunley <[email protected]>
@notgull
Copy link
Member Author

notgull commented Dec 5, 2024

LGTM aside from CI failure (due to rustwasm/wasm-bindgen#4304).

Fixed via #96

@taiki-e
Copy link
Collaborator

taiki-e commented Dec 5, 2024

Hmm, I guess it break compatibility with pre-1.51 rustc... like rust-lang/cargo#10954

@notgull
Copy link
Member Author

notgull commented Dec 5, 2024

What do you mean? We have 1.36 in the CI and it seems to pass.

@taiki-e
Copy link
Collaborator

taiki-e commented Dec 5, 2024

resolver is unknown field in 1.36, but unstable field in 1.50, so build will be fail in 1.50 even if pass in 1.36.

@taiki-e
Copy link
Collaborator

taiki-e commented Dec 5, 2024

(See also rust-lang/cargo#13505 (comment) for Cargo's behavior on unknown fields.)

@notgull
Copy link
Member Author

notgull commented Dec 5, 2024

Hmm, is there a better solution to this?

@taiki-e

This comment was marked as outdated.

@taiki-e
Copy link
Collaborator

taiki-e commented Dec 7, 2024

wasm-bindgen issue has been fixed in 0.2.98 (rustwasm/wasm-bindgen#4327), so just reverting #96 would be enough.

@taiki-e
Copy link
Collaborator

taiki-e commented Dec 7, 2024

#96 has been reverted in #97.

@notgull notgull merged commit 8419f89 into master Dec 8, 2024
14 checks passed
@notgull notgull deleted the notgull/next branch December 8, 2024 16:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants