add(ci): Check that dependencies have all been published to crates.io on release PRs #8992
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
We've mistakenly published a Github release that relies on crates from a git source thrice now, so we want to add a test that runs on release PRs to check that there are no git sources in the
Cargo.lock
file.This is a draft PR because the test still needs to be added to CI and run for PRs that have the
A-release
label.Solution
Cargo.toml
file for"source = "git+"
.TODO:
A-release
labelTests
This was tested with the
restore-internal-miner
branch to ensure that it panics when there are dependencies being pulled in from git sources.PR Author's Checklist
PR Reviewer's Checklist