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

Update to wasmtime v28 #416

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Update to wasmtime v28 #416

wants to merge 2 commits into from

Conversation

saulecabrera
Copy link
Member

No description provided.

@saulecabrera saulecabrera requested a review from jbourassa January 8, 2025 19:24
@jbourassa
Copy link
Collaborator

I also tackled the build failures in #408 -- my goal was to merge that one first.

It's stuck on windows CI failing on Ruby 3.4, but pre-built binaries still work. I investigated but not sure how to move forward, so we could allow Ruby 3.4 to fail on Windows until we get it fixed. Thoughts?

@saulecabrera
Copy link
Member Author

Sure let's merge #408 first, happy to review when you feel it's ready.

It's stuck on windows CI failing on Ruby 3.4, but pre-built binaries still work. I investigated but not sure how to move forward, so we could allow Ruby 3.4 to fail on Windows until we get it fixed. Thoughts?

Just to make sure I fully understand: if we allow Ruby 3.4 to fail on CI, we won't need to exclude it from the pre-built binaries included in the release assets? Is that correct?

@jbourassa
Copy link
Collaborator

jbourassa commented Jan 8, 2025 via email

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