zvariant 5.12 and zbus 5.16 released! 🎉
Release notes at https://github.com/z-galaxy/zbus/releases
Remote
zbus
@zbus@toot.cat
Toots about zbus crate: https://crates.io/crates/zbus
119
Followers
1
Following
16
Posts
Joined November 19, 2022
Posts
zvariant 5.11 released. This release bring support for nested dictionaries in *Dict macros, making it easy to create a strongly-typed representation of your dictionary-based types:
https://z-galaxy.github.io/zbus/faq.html#nested-dictionaries
New releaes:
* zbus 5.14
* zvariant 5.10
* zbus_xmlgen 5.3
Release notes at: https://github.com/z-galaxy/zbus/releases
Replying to
@zbus@toot.cat
looks like zbus_names broke things for folks: https://github.com/z-galaxy/zbus/issues/1665 . 😢 We're on it..
New set of releases out:
zbus 5.13
zvariant 5.9
zbus_xml 5.1
zbus_xmlgen 5.2
zbus_names 4.3
These are the first ones to be made using `release-plz` (thanks to @MarcoIeni@hachyderm.io for making this amazing tool). For now on, releasing would take much less time, allowing us to release often.
Release notes at: https://github.com/z-galaxy/zbus/releases
Thanks to our awesome new contributor, Hadi Haider, the next zvariant release will provide a `signature` macro that allows you to easily construct a D-Bus/GVariant signature from a string literal, validating it at compile-time (so you get instant feedback if you make a mistake). So you can do things like:
const SOME_SIGNATURE: Signature: signature!("a{sv}");
and be sure that if this builds, it means the signature is a valid signature string.
zbus 5.12 and zvariant 5.8 released! Include a bunch of fixes, updates and dropping of `rand` dependency.
Release notes at:
https://github.com/z-galaxy/zbus/releases/tag/zbus-5.12.0
https://github.com/z-galaxy/zbus/releases/tag/zvariant-5.8.0
PSA: our github space/org has bee renamed from "dbus2" to "z-galaxy". Two main reasons for the renaming:
1. The previous name gave people the wrong impression that the project is an attempt of a hostile takeover of the D-Bus community. That was far from the truth and the new name should help alleviate those fears.
2. The new related project that takes inspirations from zbus, zlink needed an org and has been moved under this org. While zlink is related in the sense that it also solve the same problem (IPC on Unix) and also from the same author, "dbus2" name would have likely confused folks.
https://github.com/z-galaxy
https://github.com/z-galaxy/zlink
🔖 zvariant 5.5.2 & zbus 5.7.0 released.
We listened to users' feedback and un-deprecated the SerializeDict & DeserializeDict derives. We also now recommend their use for simple cases as they can allow you to avoid a lot of boilerplate.
However, these macros have been re-written to be thin wrappers around serde derives. Although we tested these changes, there could still be some breakage. Please let us know through the usual channels, if you notice anything is off. 👍
The relevant FAQ entry in the book, has been updated accordingly: https://dbus2.github.io/zbus/faq.html#how-to-use-a-struct-as-a-dictionary
zvariant 5.5 and zbus 5.6 published!
Beside many other additions & fixes, the most important change is the deprecation of SerializeDict & DeserializeDict derive macros in favor of serde_derive macros. Confused about what that means to your existing code or how to port your code? No worries! Our book got you covered: https://dbus2.github.io/zbus/faq.html#how-to-use-a-struct-as-a-dictionary
Replying to
@zbus@toot.cat
there is now an issue to track this:
https://github.com/dbus2/zbus/issues/1144
but rest assured, you'll get deprecation warnings long before the support is dropped.
if you rely on the gvariant support in zvariant, please read this and comment if you disagree with the idea of gvariant support getting dropped from zvariant:
https://github.com/dbus2/zbus/issues/1125#issuecomment-2474819201
We now have our benchmarks running in the CI. This not only means that we now have a graphs of our performance history:
https://dbus2.github.io/zbus/dev/bench/index.html
but also, we get an alert as a comment on the commit if there is a significant enough regression detected:
😎 ⚡