Releases and the extension catalogue are fetched from hard-coded GitHub/ghcr locations. Deploys now publish to Gitea only, so update checks, archied update install and install.sh cannot see a new release, and release zips are verified only against a SHA256SUMS from the same place.
Wanted: a release and the catalogue are each a signed OCI artifact at a configurable distribution source (OCI reference + ed25519 public key), edited from the dashboard (update settings, extension settings) and seeded from [distribution] in config.toml. Channels are tags (stable, next, v). archied release keygen|publish builds, signs and pushes a release; CI uses it. install.sh installs from the same source and verifies the signature.
Done when:
a release published by CI to the default source is offered by archied update check and installed by archied update install and install.sh;
a wrong key, a tampered statement or zip, or a replayed older statement is refused;
changing either source in the dashboard takes effect without a restart;
no GitHub release or ghcr reference remains as a runtime default.
Releases and the extension catalogue are fetched from hard-coded GitHub/ghcr locations. Deploys now publish to Gitea only, so update checks, `archied update install` and `install.sh` cannot see a new release, and release zips are verified only against a SHA256SUMS from the same place.
Wanted: a release and the catalogue are each a signed OCI artifact at a configurable distribution source (OCI reference + ed25519 public key), edited from the dashboard (update settings, extension settings) and seeded from `[distribution]` in config.toml. Channels are tags (stable, next, v<version>). `archied release keygen|publish` builds, signs and pushes a release; CI uses it. `install.sh` installs from the same source and verifies the signature.
Done when:
- a release published by CI to the default source is offered by `archied update check` and installed by `archied update install` and `install.sh`;
- a wrong key, a tampered statement or zip, or a replayed older statement is refused;
- changing either source in the dashboard takes effect without a restart;
- no GitHub release or ghcr reference remains as a runtime default.
Landed in 9d8f364a: signedoci verifier shared by the catalogue and releases; release = signed statement + zip OCI artifact tagged v/next/stable; source and key in update settings and extension settings (seeded from [distribution]); archied release keygen|publish; CI publishes with RELEASE_SIGNING_KEY; install.sh pulls and verifies from the registry. Catalogue copied to git.catlow.cloud/sam/archipelago/catalogue and verifies with the built-in key. Verified: task check; local registry:2 publish/check, wrong key refused, channel replay refused, exact pin to older allowed; install.sh fetch+verify and wrong-key refusal. Open: RELEASE_SIGNING_KEY secret, first real release through CI, one manual reinstall on existing hosts, docs page in the CMS.
Landed in 9d8f364a: signedoci verifier shared by the catalogue and releases; release = signed statement + zip OCI artifact tagged v<version>/next/stable; source and key in update settings and extension settings (seeded from [distribution]); archied release keygen|publish; CI publishes with RELEASE_SIGNING_KEY; install.sh pulls and verifies from the registry. Catalogue copied to git.catlow.cloud/sam/archipelago/catalogue and verifies with the built-in key. Verified: task check; local registry:2 publish/check, wrong key refused, channel replay refused, exact pin to older allowed; install.sh fetch+verify and wrong-key refusal. Open: RELEASE_SIGNING_KEY secret, first real release through CI, one manual reinstall on existing hosts, docs page in the CMS.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Releases and the extension catalogue are fetched from hard-coded GitHub/ghcr locations. Deploys now publish to Gitea only, so update checks,
archied update installandinstall.shcannot see a new release, and release zips are verified only against a SHA256SUMS from the same place.Wanted: a release and the catalogue are each a signed OCI artifact at a configurable distribution source (OCI reference + ed25519 public key), edited from the dashboard (update settings, extension settings) and seeded from
[distribution]in config.toml. Channels are tags (stable, next, v).archied release keygen|publishbuilds, signs and pushes a release; CI uses it.install.shinstalls from the same source and verifies the signature.Done when:
archied update checkand installed byarchied update installandinstall.sh;Landed in
9d8f364a: signedoci verifier shared by the catalogue and releases; release = signed statement + zip OCI artifact tagged v/next/stable; source and key in update settings and extension settings (seeded from [distribution]); archied release keygen|publish; CI publishes with RELEASE_SIGNING_KEY; install.sh pulls and verifies from the registry. Catalogue copied to git.catlow.cloud/sam/archipelago/catalogue and verifies with the built-in key. Verified: task check; local registry:2 publish/check, wrong key refused, channel replay refused, exact pin to older allowed; install.sh fetch+verify and wrong-key refusal. Open: RELEASE_SIGNING_KEY secret, first real release through CI, one manual reinstall on existing hosts, docs page in the CMS.