-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Can't cargo publish --workspace --dry-run
if the versions already exist
#14789
Labels
A-workspaces
Area: workspaces
C-bug
Category: bug
Command-publish
S-accepted
Status: Issue or feature is accepted, and has a team member available to help mentor or review
Z-package-workspace
Nightly: package-workspace
Comments
epage
added
A-workspaces
Area: workspaces
C-bug
Category: bug
Command-publish
S-needs-team-input
Status: Needs input from team on whether/how to proceed.
Z-package-workspace
Nightly: package-workspace
labels
Nov 6, 2024
ehuss
added
S-accepted
Status: Issue or feature is accepted, and has a team member available to help mentor or review
and removed
S-needs-team-input
Status: Needs input from team on whether/how to proceed.
labels
Nov 19, 2024
In addition to being accepted, wanted to record some notes from the team's discussion
|
epage
added a commit
to epage/cargo
that referenced
this issue
Nov 21, 2024
epage
added a commit
to epage/cargo
that referenced
this issue
Nov 21, 2024
epage
added a commit
to epage/cargo
that referenced
this issue
Nov 21, 2024
epage
added a commit
to epage/cargo
that referenced
this issue
Nov 21, 2024
epage
added a commit
to epage/cargo
that referenced
this issue
Nov 21, 2024
github-merge-queue bot
pushed a commit
that referenced
this issue
Nov 21, 2024
### What does this PR try to resolve? A dry-run release process won't be bumping the versions, making it so it can't do a dry-run publish because the local/remote registries will collide. This switches it to give the local registry precedence over the remote registry to make the dry-run release process work. Fixes #14789 ### How should we test and review this PR? ### Additional information
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
A-workspaces
Area: workspaces
C-bug
Category: bug
Command-publish
S-accepted
Status: Issue or feature is accepted, and has a team member available to help mentor or review
Z-package-workspace
Nightly: package-workspace
Problem
In testing #1169 on
cargo release
now that #14721 is fixed, I came across another way you can't dry-run existing versions: the overlay registry blocks itSteps
Possible Solution(s)
Remove the restriction on the overlay which comes at the risk of it being abused.
Notes
No response
Version
cargo 1.84.0-nightly (0310497 2024-11-01)
The text was updated successfully, but these errors were encountered: