Skip to content

Releases

Components 0.9.3: notification appearance and feedback

Choose a tag to compare

@byebyebryan byebyebryan released this 05 Nov 06:55

Updates the development component bundle with the notification information styling and hardware-feedback icons accepted in the native SwayNC preview.

The changed payloads are components/appearance/render.py, components/desktop/bin/notify-volume, and components/desktop/bin/notify-brightness. Existing optional Away/Session payloads remain byte-identical to 0.9.2; publishing this archive does not change any consumer admission.

The managed core rollout uses the separately published 0.4.2 maintenance backport, retaining its 44-file inventory. This development bundle retains 48 payload files and API version 1.

Validation: 173 source tests (three existing skips), 53 isolated/native desktop checks, deterministic archive parity, site build and 1,332 browser checks; exact-source GitHub check/deployment run passed. SwayNC behavior and native rendering are validated separately in the fork.

Components 0.4.3: matched SwayNC sidebar

Choose a tag to compare

@byebyebryan byebyebryan released this 05 Nov 19:40

Adds the optional matched-card SwayNC sidebar to the qualified 0.4.x core: 75% charcoal backgrounds for the panel, information group and notifications, a defined left edge, matching card outlines, and preserved focus/critical/hover states. Older identities retain their previous appearance.

This maintenance backport changes only components/appearance/render.py and components/appearance/sddm.py; the other 42 of 44 runtime payloads match 0.4.2 exactly. It does not upgrade or select optional desktop/session features, and requires no new SwayNC fork package. Pair the stylesheet with the documented full-height/zero-margin config and built-in notification-grouping: false setting.

Validated with the component/unit, native binding, build/browser and private native SwayNC checks. Two independent builds produced the same archive.

Source: 07cf4a393314c195ace7e66d162f21d3a2f73136
Archive SHA-256: 146b4d4b81dac3804b5836348045b5b89a8fa3c62719b643a90302da8346d87a
Manifest SHA-256: 31a30ac9f11dcb4182e9b0c26e5c33ca741bdb28a2c1a195f298db8ea79dd79b

Components 0.4.2: notification appearance and feedback

Choose a tag to compare

@byebyebryan byebyebryan released this 05 Nov 06:54

Refines the accepted SwayNC information panel and notification cards while retaining the qualified core payload inventory.

  • Adds palette roles for the fork's divided time/System/Connections/Battery surface and improves notification spacing, timestamps and focus.
  • Adds speaker, microphone and brightness symbolic icons; existing changes, mute state, replacement tags, silence, 1.5-second lifetime and transient history behavior are preserved.
  • Backports exactly three changed payloads from the development bundle: components/appearance/render.py, components/desktop/bin/notify-volume, and components/desktop/bin/notify-brightness. The other 41 of 44 payloads are byte-identical to 0.4.1. API version remains 1.

Validation: 84 source tests (three existing skips), 12 component contract tests, 51 isolated/native desktop checks, deterministic archive parity, site build and 750 browser checks. The SwayNC fork separately passed data, native widget and real private-daemon/Kitty action regression gates. No new VM replay or broad hardware acceptance is claimed.

The unified information widget requires the updated SwayNC fork (Arch package revision 16); legacy dashboard widgets remain supported. Optional Away, Session and direct-control admissions stay independently selected.

Components 0.10.0: optional Close All

Choose a tag to compare

@byebyebryan byebyebryan released this 05 Nov 10:10

Adds the opt-in niri-close-all first-party utility and portable Mod+Shift+Q profile.

  • Scope is all normal windows across every workspace and output in the captured Niri session.
  • Snapshot IDs once with niri msg --json windows, then send one ordinary close-window --id request per unique ID. Applications retain save/cancel dialogs; later windows are outside the snapshot.
  • Preserve Mod+Q. No process kills, logout, retry-until-empty loop, startup service or hot-corner dependency.
  • The archive has 50 payloads: the 48 existing 0.9.3 payloads remain byte- and mode-identical, with only the helper and optional binding added.

Adopt only the helper/profile after verifying the complete archive and manifest. Personal host selection and deployment remain with the consumer. This optional release does not advance the qualified 0.4.1 full reference.

Validation: 11 Close All fixture tests; source suite, separate native controls bindings, 54 desktop checks, 85 terminal checks and 1,332 browser checks passed. No ordinary live windows were closed for testing.

Source: ef37cb1
Archive SHA-256: ea39c392dc43078db436b25a75c4cb0ad9216b34a5c663fb953e481fdde203bb
Manifest SHA-256: 51c91a0c7b6303c4482c6de0bd8c8d198b44eede65dbbd240722a95592986005

Components 0.9.2: repaint the session countdown

Choose a tag to compare

@byebyebryan byebyebryan released this 04 Nov 08:49

Fixes a frozen visible countdown in the opt-in native session screen. The five-second timer and action dispatch were running, but the numeral could stay at 5 because the renderer created local labels instead of updating the references used by the timer. Both the number and its Starting in label now update.

The regression was reproduced on 0.9.1 in a private nested Niri session: the timer reached 4 while the original screenshot still showed 5. The strengthened native check reads actual captured numerals 5, 4, 3, 2 and 1 and verifies the full delay before inert Display off dispatch. It also retains cancellation, fresh-key, remembered-selection, refusal and exactly-once checks.

Only desktop-suspend changes among the 48 payloads from 0.9.1; the other 47 payload bytes/modes remain identical. Timing, cancellation, remembered selection and lock/display ownership retain their existing behavior. Core/reference 0.4.1 and Away 0.5.0 remain independent selections.

The reference now describes Niri's default Super+Shift+P power-off-monitors action; consumer selection owns the live binding. Optional Away and countdown profiles remain explicit alternatives. Release maintenance instructions now point to the immutable release catalog without retargeting the independently qualified baseline.

Validation: 217 source tests, 30 private native GUI checks including all five rendered countdown frames, normal and portable builds and 1,332 browser checks each. No live user desktop or power/lock operation was used for testing.

Source: 41ed699.

Components 0.9.1: remember the last session action

Choose a tag to compare

@byebyebryan byebyebryan released this 04 Nov 07:53

Remembers the native session screen's last chosen action on each machine.

Reopening focuses that action and stays idle. A new click or key activation is required to start its full countdown. The choice is remembered even when the countdown is cancelled. Direct --select shortcuts also update the preference. No pending request or timer is restored.

The optional user-local preference is stored at $XDG_STATE_HOME/desktop-session/last-selection.json, normally ~/.local/state/desktop-session/last-selection.json. Missing, malformed or unreadable state falls back to Lock; unavailable storage does not block the menu. It is separate from managed configuration and consumer deployment.

Only components/desktop/bin/desktop-suspend changes among the 48 payloads from 0.9.0; the other 47 payload bytes and modes remain identical. The existing screen selection, power/lock/Away ownership, normal authorization/inhibitors and legacy routes retain their behavior. Complete reference qualification remains 0.4.1 with the Away helper/unit selected independently from 0.5.0.

Local validation: 217 source tests, 30 private nested-Niri GUI checks with inert endpoints, and 1,332 browser checks for each normal and portable build. The native regression chose Restart, cancelled, reopened with Restart focused and no timer, then required a fresh Enter to begin its countdown. Preference failure and malformed-state cases are covered without acting on the user's desktop.

Source: 6ffbdb51ea5dac644c6a434288aedf884d3ac98e.

Components 0.9.0: native session screen

Choose a tag to compare

@byebyebryan byebyebryan released this 04 Nov 07:24

Adds an opt-in native GTK session action screen for Ctrl+Alt+Delete and launcher integration.

  • Six independent actions: Lock, Display off, Suspend, Log out, Restart and Shut down.
  • Selecting an action starts a five-second cancellable countdown, then executes automatically. Cancel or Escape closes directly to the desktop; no second confirmation is required.
  • Lock establishes the existing locker then turns displays off. Display off adds no lock. Native authorization, ordinary inhibitors and existing sleep policy retain their owners.
  • Duplicate entry raises the current screen without resetting its timer. Held activation keys cannot accidentally cancel. Actual request failures are reported separately from cancellation, with an explicit fresh-timer Retry.
  • Legacy launcher and countdown routes remain available. The new screen is selected explicitly with desktop-session-menu --screen or the generated portable profile.

The complete qualified desktop/reference remains components 0.4.1, and the independent Away helper/unit remain selectable from 0.5.0. This release does not establish a new full-reference or physical-device acceptance result.

Validation at source 00d891d380b9309b2e0d5625a4bafb1548706426: 212 source tests; 29 private nested-Niri GUI checks with inert lock/power/logout endpoints; normal and portable builds and 1,332 browser checks each. GitHub CI also passed the implementation check job. Real installed locker readiness, physical input/panel return and multi-output/hotplug acceptance remain separate.

The deterministic archive contains only the 48 metadata-listed first-party payloads. Verify the archive and manifest hashes before selecting files; personal host selection and deployment stay with the consumer.

Components 0.8.1 — corrected identity provenance

Choose a tag to compare

@byebyebryan byebyebryan released this 03 Nov 19:38

This maintenance release binds the component manifest to the corrected public Git author/committer history. All 47 payload records have exactly the same bytes and modes as 0.8.0; desktop behavior and dependencies are unchanged.

The 0.6.0–0.8.0 tags now point to identity-corrected commits. Their historical release archives and checksums remain unchanged. The catalog retains their original archive source IDs and records the corrected tag source IDs separately. Current consumers should select 0.8.1 to bind their release tuple to the corrected history.

Validation passed 191 unit tests, 31 desktop checks, 85 shell checks, site build and 1332 browser checks. The payload comparison proves the same two helpers exercised by the existing 15 private native UI scenarios are delivered unchanged.

Components 0.8.0 — shared manual session confirmation

Choose a tag to compare

@byebyebryan byebyebryan released this 03 Nov 16:43

Manual lock, display-off, suspend, restart and shutdown now share the translucent full-screen five-second countdown. Escape/Cancel/focus loss cancel; repeating the same action keeps its timer; another action replaces it with a fresh countdown. A replaced request cannot execute at its old deadline.

The optional desktop-session/confirmation.toml admits the Session menu with explicit host label, seconds and display-off locking preference. Its manual power actions use one overlay without a second Rofi prompt. Log out retains Niri confirmation. Existing automatic idle, lock, hardware-button and lid owners remain independent. Legacy immediate desktop-suspend away callers remain compatible; new shortcuts use countdown --operation away.

Only desktop-suspend and desktop-session-menu changed among the 47 payload files from 0.7.0; all other bytes/modes are unchanged. Core and Away pins can remain independent.

Validation: 191 unit tests, 31 desktop checks, 85 shell checks, site build and 1332 browser checks passed. Fifteen native scenarios passed on private Xvfb/nested Niri with inert power commands, including every Session menu route, Escape, replacement, same-action duplicates and a full five-second countdown before the correct stubbed native action. No production GUI or power operation was performed during testing.

Components 0.7.0 — translucent suspend overlay

Choose a tag to compare

@byebyebryan byebyebryan released this 03 Nov 01:19

The optional manual suspend countdown now covers each connected monitor with a translucent 55% dark backdrop and large, fully opaque host, countdown and Escape text. Existing windows, including full-screen applications, remain visible beneath it. Escape, Cancel, focus loss and output hotplug cancel; repeated presses retain one timer. Ctrl+Alt+Delete still cancels before its configured Away action.

Requires PyGObject with GTK 3 and GtkLayerShell introspection (gtk-layer-shell on Arch). Remove the old floating-window rule when upgrading from 0.6.0. No persistent service is added; idle, lock, lid and hardware-button policy stay independent.

Among the 47 payload files, only desktop-suspend changed from 0.6.0. Keep existing core and Away selections when adopting this helper independently.

Validation: 179 unit tests, 31 desktop checks, 85 shell checks, site build and 1332 browser checks passed. Seven native UI/keyboard checks passed in private Xvfb/nested Niri with inert power commands, including pixel checks for the tint over a full-screen app. No production suspend was performed during testing.