Repository navigation
Conversation
GitHub grants package write per repository, so any workflow on any branch here could overwrite ghcr.io/coder/code-server, including latest and version tags. The docker job now pushes the GHCR copy to code-server-staging (Docker Hub is unchanged), signs one release attestation stating the version, the tag's commit and each image's public GHCR tags (from the same bake file), and dispatches coder/ghcr-publisher with a coder-ghcr-dispatch token. The publisher verifies the release and the attestation, then copies each image. Version tags never move; rolling tags move only for the highest stable version. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The problem. GitHub grants package write per repository.
ghcr.io/coder/code-servergives coder/code-server Write, so any workflow on any branch here (23 maintainers can push branches) can overwritelatest,4.146.0or any other tag. Thereleaseenvironment and tag rulesets don't apply toGITHUB_TOKEN.What changes in the
dockerjob. Docker Hub is unchanged.ghcr.io/coder/code-server-stagingand records each image's pushed digest (--metadata-file). No staging tag is ever read back.https://coder.com/attestations/code-server-release/v1) covers all images. It states the version, the tag's commit, and each digest's public GHCR tags, computed from the same bake file with the public registry name, so they're exactly the tags pushed today. For v4.146.0, the map matches the 24 live tags across 7 images exactly.promote-code-server.yaml) with acoder-ghcr-dispatchtoken (contents: writeonghcr-publisheronly), revokes the token, and waits for the version tags.verifyjob). Every digest must be covered by the attestation frompublish.yamlat the tag's commit.latest,debian,ubuntuand the other rolling tags move only for the highest stable version.Before merge (draft until then)
coder-ghcr-dispatchApp exists (coder/gcp#472, coder/github-org-terraform#206). Thereleaseenvironment hasCODER_GHCR_DISPATCH_APP_IDandCODER_GHCR_DISPATCH_APP_KMS_KEY;APP_KEYS_WORKLOAD_ID_PROVIDERis already there.code-server-stagingexists: coder/code-server Write,ghcr-publisherReadghcr-publisherhas Write oncode-serverAfter the next release promotes successfully: set coder/code-server to Read on
ghcr.io/coder/code-server.actionlint and shellcheck are clean. zizmor's findings on this file (1 cache-poisoning, 4 artipacked) are the same as on
main.🤖 Generated with Claude Code