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

test: use cargo --locked in CI #159

Merged
merged 1 commit into from
Mar 29, 2024
Merged

test: use cargo --locked in CI #159

merged 1 commit into from
Mar 29, 2024

Conversation

cljoly
Copy link
Owner

@cljoly cljoly commented Mar 29, 2024

This ensures:

  1. that we have more reproducible builds
  2. that CI fails if Cargo.lock is not up to date (for instance, if
    the library version was bumped but that wasn’t propagated to the
    Cargo.lock file.)

Currently, Cargo.lock is out of date with the Cargo.toml version of the
rusqlite_migration package. This PR fixes this as well.

@coveralls
Copy link

coveralls commented Mar 29, 2024

Coverage Status

coverage: 95.796%. remained the same
when pulling 5e69f46 on cargo-locked
into 61152d9 on master.

This ensures:
1. that we have more reproducible builds
2. that CI fails if Cargo.lock is not up to date (for instance, if
   the library version was bumped but that wasn’t propagated to the
   Cargo.lock file.)

Currently, Cargo.lock is out of date with the Cargo.toml version of the
rusqlite_migration package. This PR fixes this as well.
@cljoly cljoly merged commit f703306 into master Mar 29, 2024
32 checks passed
@cljoly cljoly deleted the cargo-locked branch March 29, 2024 12:53
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