Skip to content

Release 0.13.1: snap without D-Bus slots, so it passes automatic review - #34

Merged
arios4k merged 1 commit into
mainfrom
snap/no-dbus-slots
Nov 15, 2026
Merged

arios4k merged 1 commit into
mainfrom
snap/no-dbus-slots

Conversation

@arios4k

@arios4k arios4k commented Nov 15, 2026

Copy link
Copy Markdown
Owner

The Snap Store held 0.13.0 (revision 1) for manual review because of two dbus slots. This removes them:

  • Daemon (snap only): publishes its unique bus name in $XDG_RUNTIME_DIR/voltkit-daemon-address (the snap's private runtime folder) instead of owning io.github.arios4k.Voltkit.Daemon; clients (call, daemon_running) read it. snapd allows D-Bus between apps of the same snap. A second daemon still refuses to start.
  • App (snap only): runs as a non-unique GApplication, like the picker and cheat sheet already do.
  • Outside a snap nothing changes.
  • Version 0.13.1 (Cargo, spec, metainfo, What's new, man pages).

Tested: cargo test 262 passed, clippy clean, translations complete; in snap preview mode the daemon writes its address, daemon status reaches it, a second daemon refuses, daemon stop works; the APT daemon kept running throughout. Not tested in the installed snap (skipped at the author's request).

🤖 Generated with Claude Code

The Snap Store held 0.13.0 for manual review because the snap declared
two dbus slots. In the snap, the background service now publishes its
connection's unique name in a file in the snap's runtime folder and
clients call that (snapd lets apps of the same snap talk over D-Bus), and
the app runs as a non-unique GApplication. Outside a snap nothing changes:
the service still owns io.github.arios4k.Voltkit.Daemon.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@arios4k
arios4k merged commit c1c11ea into main Nov 15, 2026
4 checks passed
@arios4k
arios4k deleted the snap/no-dbus-slots branch November 15, 2026 10:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant