-
Notifications
You must be signed in to change notification settings - Fork 19
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
Address Ruby dep issues and bump to v9.0.4
#211
Conversation
* main: Bump rake-compiler from 1.2.1 to 1.2.5 Bump standard from 1.28.2 to 1.30.1 Bump rb_sys from 0.9.78 to 0.9.81 Bump rb-sys from 0.9.78 to 0.9.81 Bump wat from 1.0.64 to 1.0.69 Bump tokio from 1.28.1 to 1.29.1 Use a file to define nightly version Remove redundant `all` sub `cfg` directive chore: Pin nightly to 2023-04-23
wasmtime
to v0.9.4`wasmtime
to v9.0.4
wasmtime
to v9.0.4
v9.0.4
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.
Generally looks good to me. Left a couple of comments regarding the versions of a couple of dependencies.
ext/Cargo.toml
Outdated
wasmtime-wasi = "= 9.0.1" | ||
wasi-common = "= 9.0.1" | ||
wasi-cap-std-sync = "= 9.0.1" | ||
# For ruby-head support, we have to lock to 0.5.4 until |
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.
Should this comment be updated to say 0.5.5
?
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.
Fixed
ext/Cargo.toml
Outdated
wat = "1.0.69" | ||
tokio = { version = "1.28.2", features = ["rt", "rt-multi-thread", "time", "net"], optional = true } | ||
async-timer = { version = "1.0.0-beta.8", features = ["tokio1"], optional = true } | ||
wat = "1.0.63" |
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.
Any reason why we went back to 1.0.63
?
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.
Git conflict resolution gone wrong, fixed now
ext/Cargo.toml
Outdated
tokio = { version = "1.28.2", features = ["rt", "rt-multi-thread", "time", "net"], optional = true } | ||
async-timer = { version = "1.0.0-beta.8", features = ["tokio1"], optional = true } | ||
wat = "1.0.63" | ||
tokio = { version = "1.28.1", features = [ |
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.
Same here, any reason why we went back to 1.28.1?
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.
Git conflict resolution gone wrong, fixed now
ext/Cargo.toml
Outdated
# For ruby-head support, we have to lock to 0.5.4 until | ||
# rb-sys/stable-api-compiled-fallback feature is used in Magnus. |
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.
Is this comment still accurate? The line below has 0.5.5, and IIUC 0.6.1 also has that?
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.
Fixed
Thanks Ian 🙇 |
Due to issues surrounding ruby-head API stability, we've had to use a web of git forks to make things work with
ruby-head
, which we continuously test in production. Now that oxidize-rb/rb-sys#227 is fixed and magnus v0.5.5 is released, we can untangle that.This PR does the following:
stable-api
featureAfter this goes through, I will release a new gem version (v9.0.4).