-
Notifications
You must be signed in to change notification settings - Fork 64
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
breaking(language.rust): Switch Rust builds to wasm32-wasip1 instead of wasm32-wasi #1382
base: main
Are you sure you want to change the base?
Conversation
5283bcd
to
97ea81b
Compare
LGTM, and I've approved the PR but we'll need either @kpfleming or @philippschulte to handle merging this PR and the subsequent new major release. |
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! I compared your changes to what Kevin recommended in the ticket. We're not cutting a new release before this has been tested and approved by Kevin. I would recommend to build binaries and share it internally for testing.
b9a2a4c
to
c7c0910
Compare
30cc440
30cc440
to
c7c0910
Compare
3514cb3
to
cca0fc1
Compare
I updated the PR title to reflect the purpose of the change, since it will end up in the changelog. |
@@ -144,12 +147,17 @@ func (r *Rust) Dependencies() map[string]string { | |||
|
|||
// Build compiles the user's source code into a Wasm binary. | |||
func (r *Rust) Build() error { | |||
var wasmWasiTarget = r.config.WasmWasiTarget | |||
if wasmWasiTarget != RustWasmWasiTarget { | |||
return fmt.Errorf("your .cargo/config.toml file is configured to produce a %s binary, but that is not supported. It must be configured to produce a %s binary", wasmWasiTarget, RustWasmWasiTarget) |
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.
It looks like I was mistaken here; the value r.config.WasmWasiTarget
didn't come from .cargo/config.toml
, but from ~/.config/fastly/config.toml
(or the equivalent path on non-Linux systems). Please verify the behavior here, this error should be emitted when that file has the wrong value, not when .cargo/config.toml
has the wrong value.
If this is true, we're going to need to add new checks to validate the content of .cargo/config.toml
and rust-toolchain.toml
as well.
78969e3
to
98b8839
Compare
…m32-wasi Breaking change to support Rust 1.84 and newer BREAKING CHANGE: Only the wasm32-waip1 build target is accepted if a non default config is provided
98b8839
to
bf30e4d
Compare
Breaking change to support Rust 1.84 and newer
BREAKING CHANGE:
Only the wasm32-wasip1 build target is accepted if a non default config is provided
All Submissions:
New Feature Submissions:
Changes to Core Features:
Are there any considerations that need to be addressed for release?
this is a breaking change and will require a major version bump to prevent breakages