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

chore: Update to wasmtime v17 #285

Merged
merged 1 commit into from
Jan 30, 2024
Merged

chore: Update to wasmtime v17 #285

merged 1 commit into from
Jan 30, 2024

Conversation

saulecabrera
Copy link
Member

No description provided.

@ianks
Copy link
Collaborator

ianks commented Jan 30, 2024

Seems like ruby-head may be busted, it's a moving target so fine to ignore

@saulecabrera
Copy link
Member Author

saulecabrera commented Jan 30, 2024

@ianks Thanks for the heads up. I was thinking, would you be ok if we softened the CI criteria for Ruby head? Emit a warning instead of an error if there are failures?

@saulecabrera
Copy link
Member Author

I'll merge this as is and open a new issue to discuss options for Ruby head.

@saulecabrera saulecabrera merged commit a95d61e into main Jan 30, 2024
29 of 37 checks passed
@saulecabrera saulecabrera deleted the update-wasmtime-17 branch January 30, 2024 14:18
@saulecabrera
Copy link
Member Author

#286, feel free to leave any thoughts there and I'm happy to follow up with a PR once/if we settle on a particular solution.

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