The aur job now gets its token from the coder-automations App, which is
installed on coder/code-server-aur but can't push to the cdrci user's
fork, so the v4.146.0 job failed with "failed to push some refs to
cdrci/code-server-aur". Check out coder/code-server-aur, push the update
branch there and open the PR from it; the fork sync step goes away.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
The Docker Hub token from docker/login-action's OIDC exchange lasts 300
seconds by default. The multi-arch build takes about 10 minutes and
pushes at the end, so the v4.146.0 push failed with 401 incorrect
username or password. Ask for an hour, as coder/coder's dogfood.yaml does.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* Stop generating shrinkwraps
npm 12 removes support for shrinkwraps. Additionally, VS Code has
switched to pnpm and this will make generating the shrinkwraps less
straightforward.
Exact pins in the package.json would not be a sufficient replacement
since that does not cover transitive dependencies.
The recommendation for end user packages installed globally with npm
seems to be to be to bundle dependencies.
One idea would be to build for every platform and bundle them all, but
the whole reason we have the npm package is to support platforms for
which we are not building. If we build them, we could just add a
regular release for that platform on GitHub.
So instead for each native module we would need to add rebuild commands
in the postinstall. And ideally remove the current platform builds to
at least try keeping the tarball size down.
I am not sure it is worth the effort for what it feels like fighting
with npm, so this change does not attempt that.
* Remove devDependencies from extensions package.json
Not strictly necessary since we only install production dependencies in
the postinstall, but might as well save some bytes.
* Update Code to 1.146.0
* Support pnpm for post-install
* Get Node version from package.json
lib/vscode/remote/.npmrc no longer exists
* Switch to pnpm
VS Code recently switched to pnpm so various scripts needed to be
updated, and we might as well follow suite with code-server's own
dependencies.
In general this change just swaps out "npm" invocations for "pnpm" plus
any necessary flag changes to match but to call out some less obvious
changes:
1. The extensions directory no longer has a post-install script, so
there is no need to copy one anymore.
2. When merging the remote package.json, only copy the dependencies
since that is all we need, to avoid copying in new properties like
packageManager.
3. Remove unused publish:npm. It points to a nonexistent file anyway.
4. Remove publish:docker and just call the script directly, to avoid an
npm/pnpm dependency in a job that really has no need for it.
* Update nfpm maintainer
* 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>
* ci: mint the coder-automations App token with Cloud KMS
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* ci: validate the publish version before it reaches the shell
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
For the coder/code-server-aur update, generate a token using our GitHub
app instead.
For the others that open PRs against coder/code-server, just use
GITHUB_TOKEN since that apparently works. I also moved the env block to
the step that executes the `gh` cli rather than setting it job-level, mostly to
match the aur step, but also to make it clearer where the env var actually
applies.
PRs created through GITHUB_TOKEN apparently cannot trigger other
workflows, but I think it should be OK to trigger them manually (will
switch to the app if this becomes annoying).
* Use Docker Hub OIDC for publish workflow login
Replace the DOCKER_USERNAME/DOCKER_PASSWORD secrets with an OIDC
(workload identity federation) login to Docker Hub. The docker job now
grants id-token: write and passes the OIDC connection ID via the
DOCKERHUB_OIDC_CONNECTIONID repository variable.
* Run docker publish job in the release environment
Scopes the Docker Hub OIDC subject claim to
repo:coder/code-server:environment:release.
* Update Code to 1.139.1
* Bump proxy-addr to 2.0.8
* Add preinstall setup to build
Already had this in the release build step, not sure why it is not in
the main build step. But we started getting errors building native
modules in ci, and this seems to be why.
* Fix quick input
It types too quickly, before the input is visible.