• shater apk v0.2.24 (x86_64)
    test / go + panel tests (push) Successful in 1m42s
    release / test gate (push) Successful in 1m40s
    release / apk aarch64_cortex-a53 (push) Successful in 2m55s
    release / apk x86_64 (push) Successful in 2m56s
    release / release apk (push) Successful in 9s
    Stable

    omar released this 2026-07-28 07:50:40 -04:00 | 0 commits to main since this release

    Automated apk (OpenWrt/ImmortalWrt 25.12+) package repo for x86_64.
    Packages: shaterd (per-arch), shater-core + luci-app-shater (arch=all).
    This build: 0.2.24-r1.
    The index packages.adb is EC-signed; trust anchor shater-apk.pem (also in dist/).

    ── Add as an apk repository (rolling — install once, then just update) ──
    wget -O /etc/apk/keys/shater-apk.pem https://git.qomar.pw/omar/shater/releases/download/apk-latest-x86_64/shater-apk.pem
    echo "https://git.qomar.pw/omar/shater/releases/download/apk-latest-$(cat /etc/apk/arch)/packages.adb" > /etc/apk/repositories.d/shater.list
    apk update
    apk add luci-app-shater # pulls shater-core + shaterd too
    apk-latest-<arch> is a MOVING pointer: every release run replaces its
    assets, so the same repo line keeps serving the newest build. To pin a
    version instead, point the repo line at
    .../download/apk-vX.Y.Z-$(cat /etc/apk/arch)/packages.adb — then the
    file must be edited by hand for each upgrade.
    ── Update — ALWAYS name the packages, NEVER a bare apk upgrade ──
    apk update
    apk upgrade shaterd shater-core luci-app-shater
    A bare apk upgrade reconciles EVERY installed package against every
    configured repo and can downgrade unrelated system packages; naming them
    upgrades only those (apk-tools 3: "If list of packages is provided, only
    those packages are upgraded along with needed dependencies").
    Full guide: docs-shater/INSTALL.md §5.

    Downloads