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

ci: Check minimal version of dependencies #71

Closed

Conversation

caspermeijn
Copy link
Contributor

@caspermeijn caspermeijn commented Aug 18, 2024

Checklist

  • I have read the Contributor Guide
  • I have read and agree to the Code of Conduct
  • I have added a description of my changes and why I'd like them included in the section below

Description of Changes

Check that the minimal dependency versions specified in Cargo.toml successfully builds. cargo minimal-versions check will downgrade all dependencies and then run cargo check.

Related Issues

This branch also contains #72. I suggest to first merging that and to rebase this PR.

This crate fails to build with version 0.12.11. So the minimal version should be 0.12.15.
Check that the minimal dependency versions specified in `Cargo.toml` successfully builds. `cargo minimal-versions check` will downgrade all dependencies and then run `cargo check`.
@caspermeijn caspermeijn changed the title WIP: ci: Check minimal version of dependencies ci: Check minimal version of dependencies Aug 18, 2024
@Jake-Shadle
Copy link
Member

I'm not really interested in adding CI complexity for an unstable cargo feature, this crate is only updated on a 6-week cadence, it's not a burden to just manually bump the patch version of target-lexicon to whatever is tested in CI.

@caspermeijn
Copy link
Contributor Author

I understand your decision. I suggested the CI job as a reminder to not forget that manual work 😉

For your information, prost has been using this exact CI job for 6 months without issues: https://github.com/tokio-rs/prost/blob/df3e58e5d113a0dcf8b6735a5d04cde2d74e5df3/.github/workflows/ci.yml#L168

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