Files
Kyle CarberryandClaude Opus 5.5 e7ff0c41be ci: releases need a second approver and come only from attested builds (#8143)
* ci: releases need a second approver and come only from attested builds

The Release workflow builds the packages from a commit on main (the merge commit of an update/
PR, or a commit given to a dispatch on main) and attests each file's provenance. A member of
code-server-release-team other than the person who started the run then approves the
release-approval environment. Only that job, as the coder-release-publisher App (key in Cloud
KMS), creates the tag and publishes the release with the attested files, in one step. Releases
are immutable, so the files can't change after that, and there is no draft for anyone to edit.

publish.yaml publishes nothing until it has checked that the release came from
coder-release-publisher, is immutable, and that every file was attested by release.yaml from main.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* ci: upload release-packages directly instead of copying it

package.tar.gz is now written into release-packages next to the platform packages, so every build
job attests and uploads one flat directory without a copy.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* ci: remove a doubled blank line in release.yaml

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-19 00:54:42 +00:00
..
2026-11-18 10:09:35 -09:00
2026-11-16 12:12:06 -09:00