No description
Find a file
Repository files (latest commit first)
Filename Latest commit message Latest commit date
zed-windsurf bot de65f6f4e7
All checks were successful
Release / release (push) Successful in 8s
zed-windsurf 1.29.3-1
2026-11-21 05:21:40 +00:00
.forgejo/workflows Rename secret to RELEASE_TOKEN (FORGEJO_ prefix is reserved) 2026-11-13 10:03:19 +01:00
.gitignore zed-windsurf 1.28.1-1 2026-11-13 09:12:43 +01:00
PKGBUILD zed-windsurf 1.29.3-1 2026-11-21 05:21:40 +00:00
README.md Rename secret to RELEASE_TOKEN (FORGEJO_ prefix is reserved) 2026-11-13 10:03:19 +01:00
self-fix-prompt.md Add Forgejo release workflow with Claude Code self-fix 2026-11-13 09:54:29 +01:00
update.sh Add Forgejo release workflow with Claude Code self-fix 2026-11-13 09:54:29 +01:00
windsurf-edit-predictions.patch zed-windsurf 1.29.3-1 2026-11-21 05:21:40 +00:00

zed-windsurf

Arch package of Zed with Windsurf / Devin Desktop edit predictions. Private build, not for the AUR: it uses Windsurf's private API.

  • PKGBUILD: Arch's official zed PKGBUILD plus windsurf-edit-predictions.patch.
  • update.sh: applies the patch to the newest Zed release and bumps the PKGBUILD.
  • .forgejo/workflows/release.yaml: does that daily in CI, builds, and publishes to the Forgejo Arch registry.

Install from the registry

curl -o /tmp/forgejo.key https://git.cozygalvinism.dev/api/packages/cozyGalvinism/arch/repository.key
sudo pacman-key --add /tmp/forgejo.key
sudo pacman-key --lsign-key 'cozyGalvinism@noreply.git.cozygalvinism.dev'

Add to /etc/pacman.conf:

[cozyGalvinism.personal.git.cozygalvinism.dev]
SigLevel = Required
Server = https://git.cozygalvinism.dev/api/packages/cozyGalvinism/arch/personal/$arch

Then sudo pacman -Syu zed-windsurf. Updates arrive with normal pacman -Syu.

CI setup (once)

Repository secrets:

Secret Value
RELEASE_TOKEN Access token with write:repository and write:package
CLAUDE_CODE_OAUTH_TOKEN Output of claude setup-token

The job runs on the docker runner in an archlinux:base-devel container.

What happens on a new Zed release

  1. The daily run sees a Zed tag newer than the published package.
  2. update.sh applies the patch to that tag with git am --3way. Cargo.lock conflicts are regenerated automatically.
  3. If the patch conflicts or no longer compiles, Claude Code adapts it (instructions in self-fix-prompt.md; it may only edit files and run cargo check/cargo test and read-only git commands). The result must pass cargo check -p zed and the Windsurf tests.
  4. The package is built with makepkg and uploaded.
  5. Clean updates are committed to main. Self-fixed ones are published too, but land on an update/zed-<version> branch with a PR for you to review.

Push a pkgrel bump to main to force a rebuild of the same Zed version.

Locally

./update.sh          # SELF_FIX=1 to let Claude repair a broken patch
makepkg -si