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

Updates for latest cargo-component version #110

Merged
merged 2 commits into from
Jul 11, 2024

Conversation

benbrandt
Copy link
Contributor

@benbrandt benbrandt commented Jul 10, 2024

v0.14.0 of cargo-component requires the wasm32-wasip1 target, which is only available in Rust versions 1.78.0 and later.

This updates the RUST_VERSION, the target name, as well as pins the CARGO_COMPONENT_VERSION to hopefully avoid an issue like this in the future.

@benbrandt
Copy link
Contributor Author

benbrandt commented Jul 10, 2024

@rylev I wasn't sure if there was a reason to stay on Rust 1.76, so if there was, I created an alternate, more conservative change: #109
Feel free to keep whichever you prefer, or request changes on either.

Hopefully this fixes the CI issues in #107

Copy link
Collaborator

@rylev rylev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks great! Thanks 👍

@rylev rylev enabled auto-merge July 11, 2024 10:53
v0.14.0 of cargo-component requires the `wasm32-wasip1` target, which is only available in Rust versions 1.78.0 and later.

This updates the `RUST_VERSION`, the target name, as well as pins the `CARGO_COMPONENT_VERSION` to hopefully avoid an issue like this in the future.

Signed-off-by: Ben Brandt <benjamin.j.brandt@gmail.com>
auto-merge was automatically disabled July 11, 2024 11:13

Head branch was pushed to by a user without write access

@benbrandt
Copy link
Contributor Author

@rylev just ran into this on another project... not all of the tooling has transitioned to the new target... so we in fact need both it seems for now until the transition is complete.

@rylev
Copy link
Collaborator

rylev commented Jul 11, 2024

Indeed, this is annoying as the underlying reason we can't fully transition to wasm32-wasip1 is that rusqlite hardcodes assumptions to the wasm32-wasi target. That project is maintained but not super actively so it might be difficult to get a patch landed. In any case #100 would help address that.

@rylev
Copy link
Collaborator

rylev commented Jul 11, 2024

@benbrandt can you update the release workflow as well?

Signed-off-by: Ben Brandt <benjamin.j.brandt@gmail.com>
@benbrandt
Copy link
Contributor Author

@rylev good catch. Let me know if it looks ok

@rylev rylev merged commit 8d44bd6 into fermyon:main Jul 11, 2024
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants