Skip to content

Test minimal versions in CI with a pinned lockfile#33

Closed
ijackson wants to merge 4 commits into
magiclen:masterfrom
ijackson:minimal-lock
Closed

Test minimal versions in CI with a pinned lockfile#33
ijackson wants to merge 4 commits into
magiclen:masterfrom
ijackson:minimal-lock

Conversation

@ijackson

@ijackson ijackson commented Aug 1, 2024

Copy link
Copy Markdown
Contributor

With this MR, we:

  • Test that the dependencies declared as minimal in our Cargo.toml do work
  • Avoid trying to do our MSRV tests with recent dependencies
  • Avoid CI breakage in the 1.60 tests due to upstream changes.

4.2.0 does not build, because num-bigint doesn't:

   Compiling num-bigint v0.4.0
error[E0308]: mismatched types
  --> /home/rustcargo/.cargo/registry/src/index.crates.io-6f17d22bba15001f/num-bigint-0.4.0/src/biguint/convert.rs:70:19
   |
70 |         .div_ceil(&big_digit::BITS.into())
   |          -------- ^^^^^^^^^^^^^^^^^^^^^^^ expected `u64`, found `&_`
   |          |
   |          arguments to this method are incorrect
   |
   = note:   expected type `u64`
           found reference `&_`
@ijackson

ijackson commented Aug 1, 2024

Copy link
Copy Markdown
Contributor Author

Oh good, this fixes the CI.

Assuming you like this and merge it, I should rebase #31 and #32 so their CI is fixed. LMK when that would be convenient for you.

@ijackson

ijackson commented Aug 1, 2024

Copy link
Copy Markdown
Contributor Author

(Also, if you like this, I could make a similar MR against assert-eq-float, which would probably eliminate the override in update-minimal-versions.)

@magiclen

magiclen commented Jul 5, 2026

Copy link
Copy Markdown
Owner

Thanks for the PR.

I understand the idea, but my projects usually do not use pinned lockfiles for this kind of CI setup. I prefer to keep the normal dependency resolution, so I can quickly notice what happens when newer versions are picked up.

So I do not plan to merge this PR at the moment.

I still appreciate your suggestion.

@magiclen magiclen closed this Jul 5, 2026
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