VayuPress Updates

Reading the mirror…

Official release mirror

Updates that arrive even when GitHub doesn't.

Some hosting networks cannot reach GitHub at all. VayuPress installs on them fall back to this mirror automatically — and nothing here is taken on trust. Every release was downloaded, signature-checked and checksum-verified before it was published below, and every install verifies it again before it updates.

Latest stable release

—

Loading the release this mirror holds…

    Verified before it is held

    A mirror that stored whatever it was given could advertise an update no install would accept. This one refuses a release unless every file passes the strongest check the release offers for it.

    Sigstore signature

    The binary must be signed by the project's release workflow on main — the exact identity every install pins. A signature from any other workflow, branch or fork is refused.

    Release key

    A second, independent Ed25519 signature whose private half never leaves the project's repository secrets. Compromising the build pipeline alone does not produce it.

    Checksums

    Every file matches the SHA-256 GitHub recorded when it was uploaded, and the release's own .sha256 files where it ships them.

    A real program

    The binary must be a Linux executable image. An archive or an error page that happens to carry a valid signature is still refused.

    Files in this release

    Served from this mirror. Sizes and hashes are the ones this mirror verified.

    FileSizeSHA-256Verified by
    Loading…

    What changed

    The release notes, as published.

    Loading…

    Everything this mirror holds

    The newest stable release, the one before it — so an install that has to roll back still finds its files — and a pre-release when one is ahead of both. Refreshed from GitHub every hour.

    How an install uses it

    Nothing to configure. Every install from 3.17.66 onwards knows this address.

    1. GitHub first. The install checks GitHub directly, trying every address its resolver offers and, if all fail, re-resolving over DNS-over-HTTPS.
    2. Then this mirror. Only when GitHub cannot be reached at all does it ask here, using the same request it would have sent to GitHub.
    3. Verified again. The install checks the Sigstore signature, the release key and the checksum itself. A mirror can serve nothing, or something old — never something that installs.

    Running your own relay? Point an install at it with VAYU_UPDATE_MIRROR, or switch the mirror on for one of your own hosted domains from its page in VayuOS.

    Verify a download yourself

    Fetch the binary, its checksum and its signature bundle from the table above, then:

    sha256sum -c vayupress.sha256
    cosign verify-blob vayupress \
      --bundle vayupress.cosign.bundle \
      --certificate-identity https://github.com/johalputt/VayuPress/.github/workflows/tag-release.yml@refs/heads/main \
      --certificate-oidc-issuer https://token.actions.githubusercontent.com