[MRG] change cargo update to do a dry-run only
#2388
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov Report
@@ Coverage Diff @@
## latest #2388 +/- ##
==========================================
+ Coverage 84.08% 92.11% +8.02%
==========================================
Files 130 101 -29
Lines 15070 11522 -3548
Branches 2212 2206 -6
==========================================
- Hits 12671 10613 -2058
+ Misses 2103 614 -1489
+ Partials 296 295 -1
Flags with carried forward coverage won't be shown. Click here to find out more. 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
ctb
changed the title
cargo update to do a dry-run onlycargo update to do a dry-run only
|
is working! let's try it out on an RC... |
|
It's aliiiiive! My hypothesis appears to be correct -
|
This was referenced Dec 2, 2022
|
yessssss!!!
|
ctb
added a commit
that referenced
this pull request
Dec 3, 2022
Fixes leftover config from testing #2388
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR continues the cibuildwheel exploration that started with a fix for building the wheels (#2384 and #2385).
The saga continues like so:
When building the release candidates, we don't get "clean" rcN wheels. I think this is because when I run
cargo updatein the cibuildwheel action it's actually updating the Rust packages and we're getting a version bump from that. Yay? (See screenshot of releases page with 'dev' yada in wheel names.)This PR changes
cargo updatetocargo update --dry-runwhich should update the crates.io index without actually changingCargo.lockand pushing a version bump.We Shall See!