Skip to content
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

chore(deps): update rust to v1.81.0 #2107

Merged
merged 2 commits into from
Sep 9, 2024
Merged

chore(deps): update rust to v1.81.0 #2107

merged 2 commits into from
Sep 9, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 7, 2024

This PR contains the following updates:

Package Update Change
rust minor 1.80.1 -> 1.81.0

Release Notes

rust-lang/rust (rust)

v1.81.0

Compare Source

==========================

Language

Compiler

Libraries

Stabilized APIs

These APIs are now stable in const contexts:

Cargo

Compatibility Notes

  • Usage of the wasm32-wasi target will now issue a compiler warning and request users switch to the wasm32-wasip1 target instead. Both targets are the same, wasm32-wasi is only being renamed, and this change to the WASI target is being done to enable removing wasm32-wasi in January 2025.

  • We have renamed std::panic::PanicInfo to std::panic::PanicHookInfo. The old name will continue to work as an alias, but will result in a deprecation warning starting in Rust 1.82.0.

    core::panic::PanicInfo will remain unchanged, however, as this is now a different type.

    The reason is that these types have different roles: std::panic::PanicHookInfo is the argument to the panic hook in std context (where panics can have an arbitrary payload), while core::panic::PanicInfo is the argument to the #[panic_handler] in no_std context (where panics always carry a formatted message). Separating these types allows us to add more useful methods to these types, such as std::panic::PanicHookInfo::payload_as_str() and core::panic::PanicInfo::message().

  • The new sort implementations may panic if a type's implementation of Ord (or the given comparison function) does not implement a total order as the trait requires. Ord's supertraits (PartialOrd, Eq, and PartialEq) must also be consistent. The previous implementations would not "notice" any problem, but the new implementations have a good chance of detecting inconsistencies, throwing a panic rather than returning knowingly unsorted data.

  • In very rare cases, a change in the internal evaluation order of the trait
    solver may result in new fatal overflow errors.

Internal Changes

These changes do not affect any public interfaces of Rust, but they represent
significant improvements to the performance or internals of rustc and related
tools.


Configuration

📅 Schedule: Branch creation - "every weekend" in timezone America/Los_Angeles, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot requested a review from a team as a code owner September 7, 2024 10:58
Copy link
Contributor Author

renovate bot commented Sep 9, 2024

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

@jonathanrainer jonathanrainer merged commit 489f8df into main Sep 9, 2024
22 checks passed
@jonathanrainer jonathanrainer deleted the renovate/rust-1.x branch September 9, 2024 10:07
@jonathanrainer jonathanrainer added this to the v0.26.2 milestone Sep 9, 2024
@jonathanrainer jonathanrainer mentioned this pull request Sep 10, 2024
jonathanrainer added a commit that referenced this pull request Sep 10, 2024
## 🐛 Fixes

- **Avoid misleading warning when `--output` is not specified - @glasser
#2100**

In the release of v0.26.1 logic was added to disable the output flag if
the Federation version was less than 2.9, however this was being printed
even when the `--output` flag was not supplied. This has been corrected.

- **Improve `--graph-ref` option - @glasser #2101**

In the release of v0.26.0 the `--graph-ref` option was added to
`supergraph compose` as well as `rover dev`. However, the behaviour when
`--graph-ref` was used in conjunction with `--config` did not work as
documented. This is now fixed. Furthermore, both `rover dev` and
`supergraph compose`, when using only the `--graph-ref` option, respect
the graph ref's Federation version.

- **Further improve `--graph-ref` option - @glasser #2105**

Improves on the above by fixing some corner cases that prevented #2101
from working as intended

## 🛠 Maintenance

- **Update `eslint` to v9.10.0 - @jonathanrainer #2106**
- **Update `concurrently` to v9.0.0 - @jonathanrainer #2108**
- **Update `manylinux` CI Docker Image to v2024.09.09 - @jonathanrainer
#2110**
- **Update Rust to v1.81.0 - @jonathanrainer #2107**
- **Pass GitHub Tag to GitHub Actions Workflow - @glasser #2109**
- **Add `tower` for use with HTTP/GraphQL clients - @dotdat #2067**

## 📚 Documentation

- **Fix Glossary links - @Meschreiber @pnodet #2114**
aaronArinder pushed a commit that referenced this pull request Sep 10, 2024
- **Avoid misleading warning when `--output` is not specified - @glasser

In the release of v0.26.1 logic was added to disable the output flag if
the Federation version was less than 2.9, however this was being printed
even when the `--output` flag was not supplied. This has been corrected.

- **Improve `--graph-ref` option - @glasser #2101**

In the release of v0.26.0 the `--graph-ref` option was added to
`supergraph compose` as well as `rover dev`. However, the behaviour when
`--graph-ref` was used in conjunction with `--config` did not work as
documented. This is now fixed. Furthermore, both `rover dev` and
`supergraph compose`, when using only the `--graph-ref` option, respect
the graph ref's Federation version.

- **Further improve `--graph-ref` option - @glasser #2105**

Improves on the above by fixing some corner cases that prevented #2101
from working as intended

- **Update `eslint` to v9.10.0 - @jonathanrainer #2106**
- **Update `concurrently` to v9.0.0 - @jonathanrainer #2108**
- **Update `manylinux` CI Docker Image to v2024.09.09 - @jonathanrainer
- **Update Rust to v1.81.0 - @jonathanrainer #2107**
- **Pass GitHub Tag to GitHub Actions Workflow - @glasser #2109**
- **Add `tower` for use with HTTP/GraphQL clients - @dotdat #2067**

- **Fix Glossary links - @Meschreiber @pnodet #2114**
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants