The published archipelago/catalogue:latest no longer verifies against the default catalogue key in distribution.DefaultCatalogue. The State Store logs signature does not verify on every ListCatalogue, and /api/extensions/catalogue answers 502, so no install can browse or install from the catalogue. It is the last failing e2e check (routes) in #1789.
When it started is not known. The latest archipelago publishes were the forge package bumps for CreateIssue, so a republish signed with a different key is one candidate.
Wanted: the published catalogue verifies against the shipped key (re-sign with the right key, or rotate the shipped key in a release).
Done when: /api/extensions/catalogue lists packages on a fresh install and the routes e2e check passes.
The published `archipelago/catalogue:latest` no longer verifies against the default catalogue key in `distribution.DefaultCatalogue`. The State Store logs `signature does not verify` on every `ListCatalogue`, and `/api/extensions/catalogue` answers 502, so no install can browse or install from the catalogue. It is the last failing e2e check (routes) in #1789.
When it started is not known. The latest archipelago publishes were the forge package bumps for CreateIssue, so a republish signed with a different key is one candidate.
Wanted: the published catalogue verifies against the shipped key (re-sign with the right key, or rotate the shipped key in a release).
Done when: `/api/extensions/catalogue` lists packages on a fresh install and the routes e2e check passes.
The catalogue had been signed with the release seed, and the original catalogue seed was lost. Rotated to a new catalogue key: 76dc34a1 builds the new public key into DefaultCatalogue (shipped in v1.61.0), ARCHIPELAGO_CATALOGUE_KEY on sam/archipelago holds the new seed, and the republished catalogue:latest verifies against the new key with signedoci.Fetch. Hosts on v1.60.0 need v1.61.0 or the new key set in Extension settings.
The catalogue had been signed with the release seed, and the original catalogue seed was lost. Rotated to a new catalogue key: 76dc34a1 builds the new public key into DefaultCatalogue (shipped in v1.61.0), ARCHIPELAGO_CATALOGUE_KEY on sam/archipelago holds the new seed, and the republished catalogue:latest verifies against the new key with signedoci.Fetch. Hosts on v1.60.0 need v1.61.0 or the new key set in Extension settings.
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.
The published
archipelago/catalogue:latestno longer verifies against the default catalogue key indistribution.DefaultCatalogue. The State Store logssignature does not verifyon everyListCatalogue, and/api/extensions/catalogueanswers 502, so no install can browse or install from the catalogue. It is the last failing e2e check (routes) in #1789.When it started is not known. The latest archipelago publishes were the forge package bumps for CreateIssue, so a republish signed with a different key is one candidate.
Wanted: the published catalogue verifies against the shipped key (re-sign with the right key, or rotate the shipped key in a release).
Done when:
/api/extensions/cataloguelists packages on a fresh install and the routes e2e check passes.The catalogue had been signed with the release seed, and the original catalogue seed was lost. Rotated to a new catalogue key:
76dc34a1builds the new public key into DefaultCatalogue (shipped in v1.61.0), ARCHIPELAGO_CATALOGUE_KEY on sam/archipelago holds the new seed, and the republished catalogue:latest verifies against the new key with signedoci.Fetch. Hosts on v1.60.0 need v1.61.0 or the new key set in Extension settings.