Skip to content

Conversation

@rukai
Copy link

@rukai rukai commented Nov 1, 2025

I've tested these changes on my fork repo and all workflows pass.

The changes:

  • windows 2019 is no longer supported by github actions, so it is removed from our workflows
  • The cargo wasi repo is archived and the recent change by the rust project to rename the wasm32-wasi target to wasm32-wasip1 has broken cargo wasi as it is stuck using the now nonexistant wasm32-wasi target. While this whole thing is very silly and could probably be resolved by forking cargo-wasm and changing the name of the target, since upstream is so broken, I dont think theres much point in maintaining the CI for cargo-wasm/wasm32-wasip1. The future seems to be in cargo-component/wasm32-wasp2, so any future work on CI should be done to use that. However, I could not find an easy to run tests with cargo-component so I'm thinking its best to just disable the existing wasm32-wasip1 workflow and let someone with more wasm experience come along and fix it.

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.

1 participant