Update RDP Client#28587
Merged
rosstimothy merged 1 commit intomasterfrom Jul 5, 2023
Merged
Conversation
rosstimothy
approved these changes
Jul 3, 2023
codingllama
approved these changes
Jul 3, 2023
|
|
||
| [dependencies] | ||
| bitflags = "2.3.2" | ||
| bitflags = "2.3.3" |
Contributor
There was a problem hiding this comment.
Same remarks as #28584 (comment) - operator changes look breaking to me, but I'm unsure if it makes a difference here.
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
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 contains the following updates:
2.3.2->2.3.30.2.146->0.2.1470.3.3->0.4.01.3.4->1.4.0⚠ Dependency Lookup Warnings ⚠
Warnings were logged while processing this repo. Please check the Dependency Dashboard for more information.
Release Notes
bitflags/bitflags (bitflags)
v2.3.3Compare Source
Changes to
-=The
-=operator was incorrectly changed to truncate bits that didn't correspond to valid flags in2.3.0. This hasbeen fixed up so it once again behaves the same as
-anddifference.Changes to
!The
!operator previously calledSelf::from_bits_truncate, which would truncate any bits that only partiallyoverlapped with a valid flag. It will now use
bits & Self::all().bits(), so any bits that overlap any bitsspecified by any flag will be respected. This is unlikely to have any practical implications, but enables defining
a flag like
const ALL = !0as a way to signal that any bit pattern is a known set of flags.Changes to formatting
Zero-valued flags will never be printed. You'll either get
0x0for empty flags using debug formatting, or theset of flags with zero-valued flags omitted for others.
Composite flags will no longer be redundantly printed if there are extra bits to print at the end that don't correspond
to a valid flag.
What's Changed
Full Changelog: bitflags/bitflags@2.3.2...2.3.3
rust-lang/libc (libc)
v0.2.147Compare Source
What's Changed
IPPROTO_ETHERNETon Linux-like platforms. by @sunfishcode in https://github.com/rust-lang/libc/pull/3272New Contributors
Full Changelog: rust-lang/libc@0.2.146...0.2.147
rust-num/num-derive (num-derive)
v0.4.0Compare Source
uuid-rs/uuid (uuid)
v1.4.0Compare Source
What's Changed
borshsupport by @grovesNL in https://github.com/uuid-rs/uuid/pull/686New Contributors
Full Changelog: uuid-rs/uuid@1.3.4...1.4.0
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Renovate Bot.