Skip to content

Conversation

@akern40
Copy link
Contributor

@akern40 akern40 commented Nov 9, 2025

This crate had an MSRV of 1.64 that was enforced in the CI; however, this was done by way of an explicit pin. Now that Rust comes with an MSRV-aware resolver, we set the rust-version explicitly and add a Cargo.lock that represents the dependencies needed to support that.

We also add a weekly CI job to ensure that the MSRV still works.

This crate had an MSRV of 1.64 that was enforced in the CI; however, this was done by way of an explicit pin. Now that Rust comes with an MSRV-aware resolver, we set the `rust-version` explicitly and add a `Cargo.lock` that represents the dependencies needed to support that.

We also add a weekly CI job to ensure that the MSRV still works.
@akern40
Copy link
Contributor Author

akern40 commented Nov 9, 2025

@nilgoyette this should fix the CI issues we're seeing in #109, then we can merge that and make a release

Copy link
Contributor

@nilgoyette nilgoyette left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't know much about github workflows, but what I read doesn't seem too bad. I prefer being honest and tell you that, if you need an actual serious review, it's best to ask someone else.

@akern40
Copy link
Contributor Author

akern40 commented Nov 9, 2025

Appreciate it! I'm more just tagging for your awareness - this whole technique is copied from ndarray, so I'm pretty confident that it's fine.

Which raises a question: do you want me to tag you on stuff like this? No worries if not, I just want to make sure you aren't getting noise you don't want

@akern40 akern40 merged commit 7997e20 into rust-ndarray:master Nov 9, 2025
10 checks passed
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