-
Notifications
You must be signed in to change notification settings - Fork 50
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
fix: Merge skew and MSRV workflow #331
Conversation
@ParkMyCar would be great if you can merge my PR #282 |
1f3d349
to
9304196
Compare
@@ -30,16 +30,19 @@ jobs: | |||
- uses: Swatinem/rust-cache@v2 | |||
|
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.
There's one way to fix this without bumping MSRV:
Before the line rust-cache, do a
cargo +nightly update -Zminimal
That will guarantee that the version specified in our Cargo.toml
is used.
It needs to be done before rust-cache, to make sure it picks up the Cargo.lock generated and use it when computing cache key.
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.
Thanks for the pointer! Just added this, hopefully it works 🤞
69366de
to
2a98801
Compare
You actually don't need to install a nightly toolchain, just set |
2a98801
to
cc23263
Compare
Good to know! Since there are some open PRs I want to review and merge, for now I'm going to just bump the MSRV workflow to 1.60 so we can get CI green. |
1.60 added namespaced features and weak dependencies, which might come in handy if we want to add more integrations without a semver breaking change. And since 1.60 was released on 2022-04-07, I guess we should not invest any more work into making 1.59 work. |
With some recent PRs we hit some merge skews that prevented a test from compiling, this PR fixes those issues. It also bumps the MSRV CI workflow to 1.60, suddenly when running in 1.59 we get the following error:
... which is confusing, since the version of
rkyv
selected satisfies the dependency, and there haven't been any new versions ofrkyv
released in 5 months? It seems related to this issue, rust-lang/cargo#10189, which indicates something further down in the dependency chain is to blame. Haven't had a chance to dig further, so I bumped the MSRV workflow to 1.60