Skip to content

Releases: limahigor/omdesky-plugin

Release list

v0.2.0

Choose a tag to compare

@limahigor limahigor released this 23 Sep 15:50
9781d59

Changelog

All notable changes to the Omdesky Omarchy plugin are documented in this file.

The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.

0.2.0 - 2026-09-23

Changed

  • Breaking: requires Omdesky 0.2. The helper reads the versioned {"schema": 1, "devices": [...]} output and reports an unsupported schema instead of guessing at another format.

Added

  • Blocked devices show why they cannot connect — "Incompatible", "Access denied" or "Allow it here" — and the row subtitle gives the command to run and on which computer.
  • A CI workflow runs Omarchy's own manifest validator from a pinned, checksummed copy, scripts/validate-plugin.sh for the plugin's security checks, and the tests on every push.
  • The README documents how to remove the plugin and lists its external dependencies.

Security

  • Connections target the device's validated Tailscale address, passed after --, instead of its name, so a hostile device name can neither become a command-line option nor select another device.
  • Text from the CLI loses control, format and bidirectional characters before it reaches the bar.
  • The helper runs through /usr/bin/python3 -I, so it depends neither on its executable bit nor on PYTHON* variables or user site packages.

Fixed

  • The front square of the bar icon is no longer filled with the background colour, so the mark stays an outline on any bar theme.
  • The bar icon keeps the bar's full foreground colour instead of dimming when no device is ready.

v0.1.1

Choose a tag to compare

@limahigor limahigor released this 14 Sep 00:39
43f0a49

Changelog

All notable changes to the Omdesky Omarchy plugin are documented in this file.

The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.

0.1.1 - 2026-09-13

Security

  • Bound device command output, device count, and every retained field before data reaches QML.
  • Resolve Omdesky only from trusted package or standalone installation paths and execute it with a closed environment.
  • Supervise device queries with timeout, process-group termination, forced kill, and child reaping.