-
Notifications
You must be signed in to change notification settings - Fork 291
Upgrade wasmtime to v35.0.0 #3186
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
Conversation
fbe79f2 to
cddef14
Compare
|
Waiting to rebase onto #3187 |
b8236d2 to
d823f69
Compare
itowlson
left a comment
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.
If Alex has approved it then I reckon I can't add much but I've added it anyway!
Unless there is a compelling need for this before then let's do that. Should we move this PR back to draft in the meantime? |
d823f69 to
828db58
Compare
828db58 to
ac3b3f4
Compare
Signed-off-by: Brian Hardock <[email protected]>
ac3b3f4 to
4b72efe
Compare
|
Now that |
itowlson
left a comment
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.
![]()
Upgrade to thewasmtime v35.0.0release branch; FWIW i'm fine leaving this sit while waiting for the crates.io release in approximately 2 weeks and switching then.Upgrade to the
v35.0.0crates.io release ofwasmtimeNotably this brings in a change to wasmtime to unforbid the
teheader which allows for gRPC clients to work in Spin components.