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

Upgrade Wasmer to 2.2 (oh yeah, CosmWasm on ARM is coming 🐎) #1224

Merged
merged 11 commits into from
Mar 1, 2022

Conversation

webmaster128
Copy link
Member

@webmaster128 webmaster128 commented Feb 8, 2022

  • Upgrade to Wasmer to 2.2.0-rc1
  • Add ARM64 CI job (Linux)
  • Bump module version v2 -> v3
  • Hash Wasmer module version into file path (as discussed in Bump module serialization format to v2 #1223 (comment))
  • Upgrade to Wasmer to 2.2.0-rc2
  • Upgrade Wasmer to 2.2.0 once available
  • Write CHANGELOG entry

Closes #1210

@webmaster128 webmaster128 force-pushed the wasmer-2.2 branch 4 times, most recently from 6161228 to 1cd7ac9 Compare February 8, 2022 23:01
@webmaster128 webmaster128 changed the title Upgrade Wasmer to 2.2 Upgrade Wasmer to 2.2 (oh yeah, CosmWasm on ARM is coming 🐎) Feb 9, 2022
@fkneeland-figure
Copy link

+1 This looks great! I tested it with Provenance on an M1 mac and it works great. Anything holding it up from getting merged and tagged?

@webmaster128
Copy link
Member Author

Thanks @fkneeland-figure! I added a list to the description with the missing steps.

There is also a different dilemma we are running into right now: Wasmer is not testing with Rust < 1.56.0 anymore but we can currently not use that version in our wasmvm build system. This makes me very careful here.

@webmaster128 webmaster128 marked this pull request as ready for review March 1, 2022 15:01
@webmaster128 webmaster128 merged commit ec8b568 into main Mar 1, 2022
@webmaster128 webmaster128 deleted the wasmer-2.2 branch March 1, 2022 15:31
webmaster128 added a commit that referenced this pull request Mar 7, 2022
This is basically the same as #1224
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