chore(deps): bump the major group across 1 directory with 4 updates

[dependabot]

Bumps the major group with 4 updates in the / directory: swift-rs, ndk, zbus and zvariant.

Updates swift-rs from 0.1.0 to 1.0.7

Release notes

Sourced from swift-rs's releases.

1.0.7

Better Tauri compatibility thanks to #66

1.0.6

A lot of small fixes in this one, thanks to everyone who has been reporting issues and submitting PRs!

What's Changed

• Enable cross-compiling for macOS targets by @​HeavenVolkoff in Brendonovich/swift-rs#48
• Fix the broken cross-compile command with Xcode15 SDK by @​pewsheen in Brendonovich/swift-rs#51
• Create SRData from slices by @​irh in Brendonovich/swift-rs#52
• force using system clang unless overridden by @​Brendonovich in Brendonovich/swift-rs#54

New Contributors

• @​HeavenVolkoff made their first contribution in Brendonovich/swift-rs#48
• @​pewsheen made their first contribution in Brendonovich/swift-rs#51
• @​irh made their first contribution in Brendonovich/swift-rs#52

Full Changelog: Brendonovich/swift-rs@1.0.5...1.0.6

1.0.5

--build-path now used instead of --scratch-path (#47) by @​lucasfernog

Turns out --scratch-path doesn't do what I thought and is only available for newer Swift versions.

1.0.4

iOS Simlator Fix (#40) by @​Berrysoft

Hopefully more things work and #42 is fixed.

SRData utilities (#44) by @​LeviticusNelson

SRData can now be created from &Vec<u8>, allowing byte buffers to be passed between Rust and Swift easily.

1.0.3

Turns out that clang_rt has to be handled specially for the iOS simulator, who'd have guessed.

1.0.2

Just a quick fix for iOS support today! Thanks to @​lucasfernog we now link against clang_rt.ios, hopefully alleviating any ___isPlatformVersionAtLeast errors.

1.0.1

Just a few changes here, nothing crazy.

Swift artefacts now stored in OUT_DIR (#32)

The .build folder is now redirected to OUT_DIR, making it much easier to publish crates that contain Swift code. It also allows for...

Automatic recompilation when Swift files are modified (#28)

With compilation artefacts being away from source code, it's now safe for swift-rs to instruct Cargo to recompile Swift packages anytime their contents change!

... (truncated)

Commits

• f64a451 Merge pull request #66 from lucasfernog/fix/set-swift-target
• 0bfa71b fix(build): set Swift target triple
• 634301f Merge pull request #58 from MarvelousAnything/main
• 50a909d [Add] --arch arg to swift build command.
• 5fc773d Merge pull request #56 from DaAitch/fix-README
• 6bb3863 fix README.md dead link
• b5ed223 v1.0.6
• 1416862 Merge pull request #55 from Brendonovich/cleanup
• 6619709 cleanup + add docs
• f456dba Merge pull request #54 from Brendonovich/50-force-using-system-clang
• Additional commits viewable in compare view

Updates ndk from 0.8.0 to 0.9.0

Release notes

Sourced from ndk's releases.

ndk v0.9.0

• Move MediaFormat from media::media_codec to its own media::media_format module. (#442)
• media_format: Expose MediaFormat::copy() and MediaFormat::clear() from API level 29. (#449)
• Breaking: media_format: Mark all fn set_*() and fn str() as taking self by &mut. (#452)
• Breaking: Require all dyn Fn* types to implement Send when the FFI implementation invokes them on a separate thread: (#455)
  • audio::AudioStreamDataCallback;
  • audio::AudioStreamErrorCallback;
  • media::image_reader::BufferRemovedListener;
  • media::image_reader::ImageListener;
  • media::media_codec::ErrorCallback;
  • media::media_codec::FormatChangedCallback;
  • media::media_codec::InputAvailableCallback;
  • media::media_codec::OutputAvailableCallback.
• Drop previous Boxed callbacks after registering new ones, instead of before. (#455)
• input_queue: Add from_java() constructor, available since API level 33. (#456)
• event: Add from_java() constructors to KeyEvent and MotionEvent, available since API level 31. (#456)
• Breaking: image_reader: Special-case return statuses in Image-acquire functions. (#457)
• Breaking: image_reader: Mark ImageReader::acquire_latest_image_async() unsafe to match the safety requirements on ImageReader::acquire_next_image_async(). (#457)
• event: Implement SourceClass bitflag and provide Source::class() getter. (#458)
• Ensure all bitflags implementations consider all (including unknown) bits in negation and all(). (#458)
• Breaking: Mark all enums as non_exhaustive and fix repr types. (#459)
• Breaking: native_window: Remove redundant TRANSFORM_ prefix from NativeWindowTransform variants. (#460)
• Breaking: hardware_buffer: Convert HardwareBufferUsage to bitflags. (#461)
• bitmap: Guard BitmapCompressError behind missing api-level-30 feature. (#462)
• native_window: Require linking against libnativewindow for most API >= 26 functions. (#465)
• Breaking: audio: Merge AudioResult variant enum into AudioError. (#467)
• data_space: Add missing DataSpaceRange::Unspecified variant. (#468)
• Breaking: looper: Require Send marker when adding fd event callbacks on ForeignLooper. (#469)
• Breaking: Upgrade to ndk-sys 0.6.0. (#472)

Commits

• 49bbbba Release ndk-sys-0.6.0, ndk-0.9.0 (#472)
• 9ba82ab ndk/image_reader: Special-case return statuses in Image-acquire functions (...
• ce07460 ndk-sys: Generate against latest upstream NDK (11769913) (#471)
• 6893a70 looper: Require Send when adding fd event callbacks on ForeignLooper (#469)
• e932c84 ndk/audio: Merge AudioResult variant enum into AudioError (#467)
• 575489b ndk/native_window: Link against libnativewindow for API >= 26 functions (#465)
• ec19614 ndk/hardware_buffer: Convert HardwareBufferUsage to bitflags (#461)
• 3a25c1a ndk: Mark all enums as non_exhaustive and fix repr types (#459)
• a16f995 ndk/native_window: Remove redundant TRANSFORM_ prefix from `NativeWindowTra...
• 0b9c573 ndk: Requre all off-thread dyn Fn* callback types to implement Send (#455)
• Additional commits viewable in compare view

Updates zbus from 4.4.0 to 5.12.0

Release notes

Sourced from zbus's releases.

🔖 zbus 5.12.0

• 🚚 Update name of Github space from dbus2 to z-galaxy.
• ✨ Add Error::description method. This gives a simple description about the error.
• 🥅 Provide description for zbus::Error in DBusError. #1523
• 🐛 Remove minimum amount of required address options. Set the minimum amount of address options to 0, as per the spec. #1513
• ➖ remove rand and replace with uuid. This makes uuid mandatory for zbus, and changes the p2p feature to enable v4 of uuid.
• 📝 book: Update version of zbus in the sample Cargo.toml.
• 🧵 Launch a multi-threaded tokio runtime for blocking. Otherwise, any blocking calls in the application code can block our internal tasks. This is breaking our "we won't launch threads behind your back" promise a little but its only limited to blocking API and therefore worth the benefit of not unexpectedly stopping to work. #1512
• 🐛 Fix tracing span names showing as {}.

🔖 zbus 5.11.0

• ✨ API to specify timeouts for method calls. Add a way to specify an timeout for method calls. If set, the method calls will timeout after the specified duration, returning an error. This can be used to handle the issues with non-answering D-Bus services.
• 🩹 Add connection::socket::Split::new method, allowing Socket trait impls outside zbus.
• 📝 Mention receive_X_changes in proxy docs.

🔖 zbus 5.10.0

• ✨ Property stream will now first yield the current value.
• 🐛 Fall back to no groups rather than erroring out for peer creds.
• 📝 Fix wrong documentation in blocking Proxy methods.

🔖 zbus 5.9.0

• 🧵 Remove deadlocks in Connection name request tasks, resulting in leaks under certain circumstances.
• 🐛 When registering names, allow name replacement by default.
• ✨ Allow setting request name flags in connection::Builder.
• ✨ Proper Default impl for RequestNameFlags. This change is theoretically an API break for users who assumed the default value to be empty.
• 🧑💻 Add fdo::StartServiceReply type. In 6.0 this will be the return type of fdo::DBusProxy::start_service_by_name. For now, just provide a TryFrom<u32>.

🔖 zbus 5.8.0

• ✨ interface macro now supports write-only properties.
• ✨ Copy attributes over to receive_*_changed and cached_* methods in proxy.

🔖 zbus 5.7.1

• 🐛 Fix build on Android.
• ✏️ Trivial typo fix in error message.

🔖 zbus 5.7.0

• ✨ Add ProcessFD/pidfd to peer ConnectionCredentials.
• ✨ Enable fd passing for the channel socket. It already does supports fd passing, so all we need to do is enable it.
• 📝 Document generated prop_changed and prop_invalidated methods.
• ⬆️a Require zvariant 5.5.2.
• ⬆️ Upgrade from yanked dep versions of futures-util.

🔖 zbus 5.6.0

• 🚑️ Fix fdo::StatsProxy method return values. The return value of the methods were wrong so we fix it now. #1341

... (truncated)

Commits

• d4254d6 Merge pull request #1544 from zeenix/releases
• bd399ae 🔖 zb: Release 5.12.0
• 14fce7c 🔖 zv: Release 5.8.0
• 33cb56c 🚚 Update name of Github space from dbus2 to z-galaxy
• a00e93c ⬆️ micro: Update clap to v4.5.49 (#1540)
• 7c2baf6 Merge pull request #1538 from dbus2/renovate/actions-checkout-5.x
• 5ac2239 ⬆️ Update actions/checkout action to v5
• c9a00ea Merge pull request #1537 from DarthB/codspeed
• 562f125 use codspeed benchmarks with criterion compat layer
• 4dc5325 ⬆️ micro: Update serde to v1.0.228 (#1534)
• Additional commits viewable in compare view

Updates zvariant from 4.2.0 to 5.8.0

Release notes

Sourced from zvariant's releases.

🔖 zvariant 5.8.0

• ➖ Switch from rand to fastrand in array_value test. fastrand is already depended on indirectly.

🔖 zvariant 5.7.0

• 🐛 Reduce allocations in OwnedValue::try_from.
• ✨ Add Value::try_into_owned. Doing as few allocations as possible.
• 📝 Document when ObjectPath::into_owned clones.

🔖 zvariant 5.6.0

• 🚑️ Check signature before serializing struct as a u8. This fixes a regression that was exposed by 56cbb1f64. #1417
• 🐛 Fix build on platforms without 64-bit atomics.
• 🏷️ Add a new FilePath type to serve as a thin abstraction that handles (de)serialization of a file path as a byte array, since en/decoding of strings is limited to only UTF-8 characters in both D-Bus format and serde API. #977

* 🔖 zvariant 5.5.3

• 🚑️ Fix use of empty structs with SerializeDict. #1375

🔖 zvariant 5.5.2

• ✨ Un-deprecate SerializeDict & DeserializeDict. For simple cases, they're pretty good and now that we've made them wrappers around serde derives, maintenance shouldn't be an issue. We will no longer need to add new attributes because if people woule want any, they should just use the serde derives directly.
• ✨ SerializeDict & DeserializeDict now wrappers around serde derives.

🔖 zvariant 5.5.1

A bugfix release, fixing the breakage from 5.5.0 (now yanked):

• 🚑️ Use pub use instead of a type alias. for as_value::{Deserialize, Serialize}. They structs expose their main internal field and get instantiated directly in the using code and that seems to break the API compatiblity when using type aliases.
• 🔥 Drop as_value::{Serialize, Deserialize} re-export. This was an accident. We don't want them on the crate-level.

🔖 zvariant 5.5.0

• 🚑️ Ensure empty array is (de)serialized the same way as unit type.
• ✨ Add as_value module. This new module provides API that can be used with serde::{Serialize::Deserialize} derives to (de)serialize a value as a Value (variant type). This is espcially useful for (de)serialization of structs as a dictionary (a{sv}).
• 🗑️ Deprecate SerializeDict & DeserializeDict macro. Now that user can directly use serde::{Serialize, Deserialize} for dict encoding of a struct, we don't need these anymore.
• 🚚 Move SerializeValue & DeserializeValue into as_value & rename. These types belong in as_value module and given the context, we can just name them Serialize and Deserialize. We still provide type aliases to not break the API.
• 📝 Improve Str docs.
• 🚑️ Correctly handle identifier de for gvariant. We basically just need to do it exactly the same way as we do for the D-Bus format.
• 🚑️ More robust deserialization of variants. Our deserializers rely on a specific behavior from the Value's Deserialize impls, and that fails when Value is being deserialized in a generic way (through deserialize_any or deserialize_ignored_any) and we end up with overflowing the stack. This happens for example when ignoring unknown fields/entries. Unfortunately, in case of GVariant we now no longer error out if a null byte is missing in a string type. You can blame Allison Lortie for removing the null-termination from a signature only when it is encoded in a variant but not otherwise. :)
• ✨ Allow structs to be serialized as dictionaries.
• ✨ zb,zn,Implement Borrow for Owned* types. Implementing Borrow makes things such as using Owned* types as keys easier, and it was more-or-less designed for this type of scenario anyway. Although it comes with some stringent requirements (i.e. traits implemented on the owned type need to have identical behavior to the borrowed type), all of these types are already rather thin wrappers to begin with.
• ➖ Drop static_assertions dep.
• 🐛 fix wrong lifetime when creating a Value from &Vec and &[]. When creating a Value from a borrowed vec or slice using Value's From implementation, the compiler would wrongfully assume, that the created value has the same lifetime, even though the input gets cloned when creating the Array struct. This commit makes the impl assign a new lifetime to the cloned value.
• ✨ Implement rename/rename_all when deriving Value/OwnedValue. Previously, setting these values would not apply to implementations of From and TryFrom when converting between a type and Value/OwnedValue. This change makes it so using rename or rename_all will apply to these traits. #320
• ✨ *Value derive macros:
  • Support string encoding for enums.
  • Support enum variants without explicit values.
• 🐛 Prefix a local variable w/ __ so it doesn't conflict w/ fields. ..in the struct deriving DeserializeDict. #1252.

... (truncated)

Commits

• 14fce7c 🔖 zv: Release 5.8.0
• a00e93c ⬆️ micro: Update clap to v4.5.49 (#1540)
• 7c2baf6 Merge pull request #1538 from dbus2/renovate/actions-checkout-5.x
• 5ac2239 ⬆️ Update actions/checkout action to v5
• c9a00ea Merge pull request #1537 from DarthB/codspeed
• 562f125 use codspeed benchmarks with criterion compat layer
• 4dc5325 ⬆️ micro: Update serde to v1.0.228 (#1534)
• 921e0e9 ⬆️ micro: Update windows-sys to v0.61.2 (#1535)
• 54dea5d ⬆️ micro: Update quote to v1.0.41 (#1533)
• c407d50 ⬆️ micro: Update camino to v1.2.1 (#1532)
• Additional commits viewable in compare view

Note

Bump major versions of ndk, zbus, zvariant, and swift-rs dependencies

• Updates android-companion/Cargo.toml: ndk 0.8 → 0.9
• Updates linux-dbus/Cargo.toml: zbus and zvariant v4 → v5
• Updates macos-share/Cargo.toml: swift-rs 0.1 → 1.0

^{Macroscope summarized 2fbbac0.}

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	cargo/​zbus@​4.4.0 ⏵ 5.12.0	+1
	cargo/​zvariant@​4.2.0 ⏵ 5.8.0

View full report

[chatgpt-codex-connector]

Codex usage limits have been reached for code reviews. Please check with the admins of this repo to increase the limits by adding credits.
Repo admins can enable using credits for code reviews in their settings.

[kilo-code-bot]

WARNING: swift-rs 1.0 removes the 0.1 build_utils free-function API that build.rs depends on.

build.rs (lines 45-54) calls swift_rs::build_utils::{link_swift, link_swift_package} — the swift-rs 0.1 free-function API. swift-rs 1.0 (the "newer line" your own build.rs comment contrasts against) replaced this with the SwiftLinker builder API, so cargo build -p byteport-macos-share --features link-swift on macOS will fail to compile. Either migrate build.rs to the 1.0 SwiftLinker API or keep swift-rs = "0.1" until that migration lands.

---

Reply with @kilocode-bot fix it to have Kilo Code address this issue.

[kilo-code-bot]

WARNING: Major bump to zbus 5 — verify the scaffold still compiles against the v5 API.

This crate's source (src/ipc.rs, src/dbus.rs) uses zbus::ConnectionBuilder::session(), zbus::Proxy::new(...), zbus::SignalStream, and the #[dbus_interface(signal)] macro. zbus 5 is a major release with breaking changes (e.g. ConnectionBuilder reworked into connection::Builder, connection-constructor changes). cargo check --workspace does not exercise this crate on non-Linux CI, so confirm a Linux target still builds before merge.

---

Reply with @kilocode-bot fix it to have Kilo Code address this issue.

[kilo-code-bot]

SUGGESTION: Stale rationale comment now contradicts the version bump.

The comment block (lines 19-22) states "zbus 4 is selected over 5 because 4 is the last release line that pins tokio as an optional feature (rather than a hard default)". This crate now pins zbus = "5" (line 24), so that justification is void. Update the comment to reflect that zbus 5 is selected via default-features = false, features = ["tokio"].

---

Reply with @kilocode-bot fix it to have Kilo Code address this issue.

[kilo-code-bot]

Code Review Summary

Status: 3 Issues Found | Recommendation: Address before merge

Overview

Severity	Count
CRITICAL	0
WARNING	2
SUGGESTION	1

Issue Details (click to expand)

WARNING

File	Line	Issue
ffi/macos-share/Cargo.toml	28	swift-rs 1.0 removes the 0.1 build_utils free-function API that build.rs depends on
ffi/linux-dbus/Cargo.toml	22	Major bump to zbus 5 — verify the scaffold source still compiles against the v5 API

SUGGESTION

File	Line	Issue
ffi/linux-dbus/Cargo.toml	19	Stale rationale comment now contradicts the version bump

Files Reviewed (4 files)

• Cargo.lock — generated lockfile; excluded from inline review
• ffi/android-companion/Cargo.toml — no issues
• ffi/linux-dbus/Cargo.toml — 3 issues (2 WARNING, 1 SUGGESTION)
• ffi/macos-share/Cargo.toml — 1 issue (WARNING)

Fix these issues in Kilo Cloud

Previous Review Summary (commit cbf573c)

Current summary above is authoritative. Previous snapshots are kept for context only.

Previous review (commit cbf573c)

Status: 3 Issues Found | Recommendation: Address before merge

Overview

Severity	Count
CRITICAL	0
WARNING	2
SUGGESTION	1

Issue Details (click to expand)

WARNING

File	Line	Issue
ffi/macos-share/Cargo.toml	28	swift-rs 1.0 removes the 0.1 build_utils free-function API (link_swift, link_swift_package) that build.rs (lines 45-54) depends on; the --features link-swift macOS build path will fail to compile. Migrate build.rs to the 1.0 SwiftLinker API or keep swift-rs = "0.1".
ffi/linux-dbus/Cargo.toml	24	Major bump to zbus 5 — the scaffold source (ipc.rs, dbus.rs) uses ConnectionBuilder::session(), Proxy::new(), SignalStream, and #[dbus_interface(signal)], all of which changed in zbus 5. Verify a Linux target still compiles (CI won't exercise this off-Linux).

SUGGESTION

File	Line	Issue
ffi/linux-dbus/Cargo.toml	19	Stale rationale comment (lines 19-22) says "zbus 4 is selected over 5 because 4 pins tokio as an optional feature" — now contradicted by zbus = "5" on line 24. Update the comment.

Considerations (not inline)

• ffi/android-companion/Cargo.toml:15 — ndk = "0.9" is declared but unused in src/lib.rs (only jni is referenced). The bump is harmless but ndk appears to be a dead dependency here.
• ffi/macos-share/Cargo.toml comment block (lines 14-23) and src/lib.rs:3 still describe the swift-rs 0.1 free-function API; they now contradict the 1.0 bump and should be updated alongside the build.rs migration.
• zvariant 4 -> 5 is pulled in transitively via zbus 5; no direct zvariant API usage was found in the scaffold, but it rides the same breaking-change surface as zbus.

Files Reviewed (4 files)

• Cargo.lock — generated lockfile; updated consistently with the bumps (excluded from inline review)
• ffi/android-companion/Cargo.toml — 1 issue (Consider)
• ffi/linux-dbus/Cargo.toml — 2 issues (1 WARNING, 1 SUGGESTION)
• ffi/macos-share/Cargo.toml — 1 issue (WARNING); build.rs/src/lib.rs reviewed for context

Fix these issues in Kilo Cloud

---

_{Reviewed by step-3.7-flash · Input: 163.9K · Output: 18.7K · Cached: 892K}

[codeant-ai]

Skipping PR review because a bot author is detected.

If you want to trigger CodeAnt AI, comment @codeant-ai review to trigger a manual review.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud