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
..
2023-08-07 19:02:54 +00:00
2026-02-10 07:33:01 -09:00
2022-09-09 15:15:39 -07:00
2026-08-20 13:24:49 -08:00
2026-11-10 15:49:12 -09:00
2022-04-12 11:32:49 -07:00
2023-02-13 16:52:48 -06:00
2026-11-18 10:09:35 -09:00
2024-10-17 20:32:21 -08:00
2022-02-01 09:45:19 -07:00

code-server

"GitHub Discussions" "Join us on Slack" Twitter Follow Discord See latest

Run VS Code on any machine anywhere and access it in the browser.

Screenshot Screenshot

Highlights

  • Code on any device with a consistent development environment
  • Use cloud servers to speed up tests, compilations, downloads, and more
  • Preserve battery life when you're on the go; all intensive tasks run on your server

Requirements

See requirements for minimum specs, as well as instructions on how to set up a Google VM on which you can install code-server.

TL;DR: Linux machine with WebSockets enabled, 1 GB RAM, and 2 vCPUs

Getting started

There are four ways to get started:

  1. Using the install script, which automates most of the process. The script uses the system package manager if possible.
  2. Manually installing code-server
  3. Deploy code-server to your team with coder/coder
  4. Using the code-server feature for devcontainers, if you already use devcontainers in your project.

If you use the install script, you can preview what occurs during the install process:

curl -fsSL https://code-server.dev/install.sh | sh -s -- --dry-run

To install, run:

curl -fsSL https://code-server.dev/install.sh | sh

When done, the install script prints out instructions for running and starting code-server.

Note

To manage code-server for a team on your infrastructure, see: coder/coder

We also have an in-depth setup and configuration guide.

Questions?

See answers to frequently asked questions.

Want to help?

See Contributing for details.

Hiring

Interested in working at Coder? Check out our open positions!

For Teams

We develop coder/coder to help teams to adopt remote development.