automagik-dev/genie to automagik-si/genie.automagik-si/genie. Every check in Genie compared that name with automagik-dev/genie: the release pipeline's own verification, install.sh, and genie update in every installed binary. So:v6.261108.1 (stable) and v6.261109.9 (dev).12source-repository-id: 1030039430 source-repository-owner-id: 245047546
automagik-si/genie or automagik-dev/genie, with the same workflow file and branch. Any other name is refused, and so is a certificate without both ids. The OIDC issuer is checked as before. genie update, install.sh and scripts/verify-release.sh all apply this rule, and the release pipeline publishes under automagik-si/genie again. Security and releases lists the full pinned identity..well-known/v2/latest.json and .well-known/v2/dev.json, and new releases are published there only..well-known/latest.json and .well-known/dev.json stay on v6.261108.1 (stable) and v6.261109.9 (dev), the last releases from before the fix. No release changes them again.6.261108.1, dev up to 6.261109.9. Such a binary reads the two frozen files and accepts only release evidence that names automagik-dev/genie, so it cannot verify a release signed under the new name.genie --version prints 6.261108.1 or lower on stable, 6.261109.9 or lower on dev, and genie update reports that the install is up to date while newer releases exist. The output is on stdout and the exit code is 0:1✔ Already up to date (v6.261108.1, channel stable)
6.261108.1 (stable) or 6.261109.9 (dev) first, and then reports the same.automagik-si/genie.automagik-si/genie, with cosign and slsa-verifier installed:1scripts/verify-release.sh <tag>
genie update prints something this page does not cover, open an issue at automagik-si/genie with the full output. For a suspected vulnerability, report privately as described in Security and releases.