Add Rust 1.90.0 announcement #1691
Open
+107
−0
Conversation
This file contains hidden or 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
|
@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 |
Kobzol
reviewed
Sep 7, 2025
Kobzol
reviewed
Sep 8, 2025
Co-authored-by: Jakub Beránek <berykubik@gmail.com>
jieyouxu
approved these changes
Sep 8, 2025
alex-semenyuk
approved these changes
Sep 8, 2025
Kobzol
approved these changes
Sep 10, 2025
|
|
||
| GitHub will soon [discontinue][gha-sunset] providing free macOS x86\_64 runners for public repositories. Apple has also announced their [plans][apple] for discontinuing support for the x86\_64 architecture. | ||
|
|
||
| In accordance with these changes, as of Rust 1.90, the project has [demoted the `x86_64-apple-darwin` target][rfc] from [Tier 1 with host tools](https://doc.rust-lang.org/stable/rustc/platform-support.html#tier-1-with-host-tools) to [Tier 2 with host tools](https://doc.rust-lang.org/stable/rustc/platform-support.html#tier-2-with-host-tools). This means that the target, including tools like `rustc` and `cargo`, will be guaranteed to build but is not guaranteed to pass our automated test suite. |
There was a problem hiding this comment.
Suggested change
| In accordance with these changes, as of Rust 1.90, the project has [demoted the `x86_64-apple-darwin` target][rfc] from [Tier 1 with host tools](https://doc.rust-lang.org/stable/rustc/platform-support.html#tier-1-with-host-tools) to [Tier 2 with host tools](https://doc.rust-lang.org/stable/rustc/platform-support.html#tier-2-with-host-tools). This means that the target, including tools like `rustc` and `cargo`, will be guaranteed to build but is not guaranteed to pass our automated test suite. | |
| In accordance with these changes, as of Rust 1.90, we have [demoted the `x86_64-apple-darwin` target][rfc] from [Tier 1 with host tools](https://doc.rust-lang.org/stable/rustc/platform-support.html#tier-1-with-host-tools) to [Tier 2 with host tools](https://doc.rust-lang.org/stable/rustc/platform-support.html#tier-2-with-host-tools). This means that the target, including tools like `rustc` and `cargo`, will be guaranteed to build but is not guaranteed to pass our automated test suite. |
Not sure if people know what "the project" is here.
epage
approved these changes
Sep 10, 2025
| 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.
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.
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
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.
cc @rust-lang/release
Rendered