-
Notifications
You must be signed in to change notification settings - Fork 5
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
Conversation
There was a problem hiding this 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 👍
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>
Head branch was pushed to by a user without write access
b06f99e
to
dbbefe9
Compare
@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. |
Indeed, this is annoying as the underlying reason we can't fully transition to |
@benbrandt can you update the release workflow as well? |
Signed-off-by: Ben Brandt <benjamin.j.brandt@gmail.com>
51b09d9
to
954eba4
Compare
@rylev good catch. Let me know if it looks ok |
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 theCARGO_COMPONENT_VERSION
to hopefully avoid an issue like this in the future.