-
Notifications
You must be signed in to change notification settings - Fork 306
Add Rust 1.90.0 announcement #1691
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
base: master
Are you sure you want to change the base?
Conversation
@rustbot ping relnotes-interest-group |
Hi relnotes-interest-group, this PR adds a release blog post. Could you review cc @alex-semenyuk @jieyouxu @joshtriplett @Kobzol @lcnr @traviscross |
Co-authored-by: Jakub Beránek <[email protected]>
the crates in a workspace in the right order (following any dependencies | ||
between them). This has long been possible with external tooling or manual | ||
ordering of individual publishes, but this brings the functionality into Cargo | ||
itself. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we call out the caveat that the publish is not atomic and network or server side errors can leave you in a partially published state?
This is true for existing workarounds but people might have a different expectation with it built in.
`cargo publish --workspace` is now supported, automatically publishing all of | ||
the crates in a workspace in the right order (following any dependencies | ||
between them). This has long been possible with external tooling or manual | ||
ordering of individual publishes, but this brings the functionality into Cargo |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we are comparing to existing approaches, is it worth it to call out how this improves on those?
The biggest change is in the verify step which can verify everything before publishing
- for a real publish, this reduces the chance of it failing in a partially published state
- for dry-run, you can now run the verify
Co-authored-by: Jakub Beránek <[email protected]>
cc @rust-lang/release
Rendered