chore(deps): update rust crate zbus to v5 (v2) #2078
Closed
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:
4->5Release Notes
dbus2/zbus (zbus)
v5.1.1: π zbus 5.1.1Compare Source
async-processdependency toasync-iofeature, instead of the target OS. This fixestokiousers (a big majority of our users) needlessly depending on it along with a bunch of itsdependencies.
lot of noise in the logs.
v5.1.0: π zbus 5.1.0Compare Source
rust-versionto1.80. #β1107unixexectransport.Commandstdio socket type. This socket communicates with a spawned child process viaits standard input and output streams.
winnow.v5.0.1: π zbus 5.0.1Compare Source
zvariant_utilsdep. We don't always releasezvariant_utilstogether with othercrates, so unlike the macros crates, the versions don't need to be tied together. This will also
allow us to bring
zvariant_utilsimprovements to users without having to release all dependentpackages as well.
v5.0.0: π zbus 5.0.0Compare Source
encoding and decoding.
proxymacro respects visibility. This includes all types generated byproxy. Unfortunatelythis means that the existing code will have to set the visiblity explicitly to
pubif theywere relying on the generated proxy to be public.
DBUS_COOKIE_SHA1auth mechanism. #β727sha1crate as a dependency, which can be problematic for some users. #β543EXTERNALis not an option, you might as well just useANONYMOUS.authentication mechanisms with one of them being no-authentication, this really makes sense
since we can just autodetect what authentication method to use for a specific socket type on a
specific platform. This also simplifies the handshake logic and will allow us to pipeline the
whole client-side handshake in the future, when we can drop the xdg-dbus-proxy workarounds. #β781
same type of arguments.
fdoAPI.interfacenow generates a trait, Signals, that provides the same signalmethods as user specifies but w/o the
SignalEmitterargument (#β871). The macro also generates2 implementations of this trait for:
method.
SignalContext::emit. Add a new method to SignalContext that allows emitting a signal fora given interface and singal name.
mechanism. We'll use this in a following commit to avoid an allocation.
should be used with it. The implementation can choose this based on the socket type and the
target platform.
be private.
SignalContexttoSignalEmitter. Since now this emits signals, this is a moreappropriate name. We keep a deprecated
SignalContexttype alias as well as thesignal_contextattribute ofinterfacefor not completely breaking the existing code.AuthMechanismin the root asdeprecated.
the conversion to NonZeroU32 panics. #β946
the
ProxyAPI.p2pfeature is enabled.serde_bytesCargo feature. This is just a proxy feature forzvariant'sserde_bytesfeature. #β1052
blocking-apitozbus&zbus_macros. When enabled, thezbus::blockingmodule is available. When disabled,proxymacro ignores the value of
gen_blockingattribute and doesn't generate blocking proxy. Thisfeature is enabled by default.
caminofeature as proxy for zvariant feature of the same name.sha1crate.futures-sink.randnow an optional dependency. It is only enabled ifp2pfeature is enabled. This meansthat
randdependency is dropped for typical users.blockingmodule docs.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 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.
This PR was generated by Mend Renovate. View the repository job log.