Skip to content

Releases

Niri Plus fork release 2

Choose a tag to compare

@byebyebryan byebyebryan released this 15 Nov 00:08
d2a4bc7

Promotes the accepted history-retention trial as swaync-bryan 0.12.6-20.

  • Adds independent history-retention and history-retention-critical limits, in integer seconds. Both default to 0 (unlimited); personal one-hour settings remain consumer policy.
  • Receipt age includes suspend. Accepted replacements restart age, resident notifications are exempt, and an active inline reply defers removal.
  • History expiry preserves a live popup and its actions. Notifications close once both views are gone; config reload recalculates deadlines without changing popup timeouts.
  • Omits the notification protocol's persistence capability while either history limit is enabled.

The maintained source tree is identical to the accepted RC1 source. Development commits were consolidated through one squash-merged feature PR, followed by a separate recipe PR; published history and previous release tags are preserved.

The pinned source and final recipe are independently qualified by required hosted checks. The published source archive was verified against Git, built and tested separately; canonical Arch packaging runs its own tests. Assets include the exact source/recipe archives, package, build metadata, checksums and readiness receipts. Upgrading restarts SwayNC and clears its in-memory history.

Source: 96a2a9c4574e26fc6d6839a0e19d506a7638898e (PR #4).
Recipe: d2a4bc709b7ea77567ca50fac9b1001088f90815 (PR #5).

This remains based on upstream development commit b8017a4d1a53debdf0e8766628fb80357eae31e7 with Meson version 0.12.6, rather than the upstream v0.12.6 release tag.

Niri Plus fork release 1

Choose a tag to compare

@byebyebryan byebyebryan released this 08 Nov 01:44

First maintained release of the Niri Plus SwayNC fork. It consolidates the accepted activation, retained-card actions, clock and unified information widgets, including paired networking, without changing their runtime source or appearance.

main is an exact upstream mirror. niri-plus is the protected default branch with one source baseline and one separate package-recipe commit. Future downstream changes use squash PRs; upstream integrations preserve merge ancestry.

  • Upstream development baseline: b8017a4d1a53debdf0e8766628fb80357eae31e7 (Meson version 0.12.6; not the upstream v0.12.6 release tag).
  • Source: 7e0ea67572a5c98412572c1ef3eb6920354fa1d6; archive SHA-256 aa54161e698a434f8b1b624b1cdbdc214d2516e56a708e31217dce4ccb413408.
  • Recipe/tag target: 8998ab49dc71e2c1353d5518cd8cd30191f41d18; archive SHA-256 577103af2aa99d158416008430f54eb761f578e9c0401395528224c690e1494a.
  • Package: swaync-bryan 0.12.6-18; package numbering remains monotonic for existing installations.

The exact source and recipe passed all five required hosted contexts. Native GTK, private Niri/owned-client lifecycle and retained-action checks passed; the anonymous source archive matched all 152 tracked files and passed its clean build/four Meson suites. Strict release readiness reports source-ancestor. The attached canonical Arch package came from the exact-recipe CI run recorded in its receipt.

Build/install from the qualified recipe in this tag, following the Arch instructions. Source, recipe, canonical package and readiness receipts are attached with checksums. A service restart clears in-memory notification history.

Managed rollout is complete and verified on Starship, Snap and Carbon, including configuration/theme and DND/panel preservation, other service generations, exact recipe stamps and repeat-installer idempotence. The fixed Niri Plus rollout record keeps managed adoption separate from the dated package-17 native/reference media. The attached reset receipt captures publication-time cutover; rollout completed afterward. This reset does not claim a new physical or complete fresh-Arch replay.

The two earlier releases, three old tags and reviewed obsolete branches have been retired after the current guide and consumers migrated. Verified local recovery bundles, archives and packages are retained, including a second verified copy on Snap.

All five required maintained-branch checks pass. The pure upstream mirror keeps upstream workflow definitions; its inherited Fedora/lint runs failed in this fork and are recorded separately from maintained source/package qualification.