Repository navigation
Niri Plus fork release 1
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-256aa54161e698a434f8b1b624b1cdbdc214d2516e56a708e31217dce4ccb413408. - Recipe/tag target:
8998ab49dc71e2c1353d5518cd8cd30191f41d18; archive SHA-256577103af2aa99d158416008430f54eb761f578e9c0401395528224c690e1494a. - 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.