Skip to content

Conversation

@dhardy
Copy link
Member

@dhardy dhardy commented Feb 8, 2026

Trusted-publishing failed recently due to the lockfile being outdated (because the rand version number in Cargo.toml had been changed and for whatever reason this must be listed in Cargo.lock too).

This test should ensure CI fails before trying to run a publish job should this happen again.

(Alternatively, we could just remove Cargo.lock from version control.)

@dhardy
Copy link
Member Author

dhardy commented Feb 8, 2026

Success: the new test failed.

I'll now fix up Cargo.lock.

@dhardy dhardy requested a review from newpavlov February 8, 2026 14:22
- uses: actions/checkout@v6
- uses: dtolnay/rust-toolchain@stable
- run: cargo check --workspace
- run: test "$(git status --porcelain)" == ""
Copy link
Member

Choose a reason for hiding this comment

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

I think we can remove the last command and use cargo check --workspace --locked instead.

Copy link
Member Author

Choose a reason for hiding this comment

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

So there is a command for this; well spotted.

Copy link
Member

Choose a reason for hiding this comment

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

Not quite. It still downloads and checks all dependencies which is a bit redundant in our case.

@dhardy dhardy force-pushed the push-srpmxmytyyqr branch from 378d0c7 to 989872d Compare February 9, 2026 11:05
@dhardy dhardy merged commit 7e9754b into master Feb 9, 2026
17 checks passed
@dhardy dhardy deleted the push-srpmxmytyyqr branch February 9, 2026 11:30
newpavlov added a commit to rust-random/getrandom that referenced this pull request Feb 9, 2026
newpavlov added a commit to RustCrypto/utils that referenced this pull request Feb 9, 2026
Checks that Cargo.lock was properly updated after repository crate
versions were changed.

Based on rust-random/rand#1739
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