Skip to content

RELEASING.md

Latest commit

 

History

History
74 lines (59 loc) · 3.57 KB

RELEASING.md

File metadata and controls

74 lines (59 loc) · 3.57 KB
Raw

Releasing this fork

This is Replo's fork of opencode. It ships the same way upstream does — a self-contained binary that a curl | bash install script downloads from GitHub Releases, not via npm. The root install script points at replohq/replopencode releases instead of anomalyco/opencode.

There is no CI release path. The inherited .github/workflows/publish.yml is gated if: github.repository == 'anomalyco/opencode' and never fires here. Every release is built locally and uploaded by hand — don't go looking for a workflow_dispatch to trigger.

Tags

Tags are vX.Y.Z-N. The base X.Y.Z is the upstream version this fork is built on; -N is our patch number on that base, 1-indexed. A new fork change on the same base bumps -N. Re-applying the fork onto a new upstream base resets it to -1.

Cut a release

From dev, after merging your change. The OPENCODE_TARGETS filter keeps you from cross-compiling all 12 targets — the Windows and musl cross-builds from macOS are flaky, and Replo doesn't consume them.

OPENCODE_VERSION=<v> \
OPENCODE_TARGETS="opencode-linux-x64,opencode-linux-x64-baseline,opencode-linux-arm64,opencode-darwin-arm64" \
  bun run --cwd packages/opencode build --skip-embed-web-ui

cd packages/opencode/dist
for t in opencode-linux-x64 opencode-linux-x64-baseline opencode-linux-arm64; do
  ( cd "$t/bin" && tar -czf "../../$t.tar.gz" * ); done
( cd opencode-darwin-arm64/bin && zip -qr ../../opencode-darwin-arm64.zip * )
( shasum -a 256 *.tar.gz *.zip 2>/dev/null || sha256sum *.tar.gz *.zip ) > SHA256SUMS

gh release create v<v> --repo replohq/replopencode --target dev --latest \
  --title "Replopencode v<v>" --notes "..." \
  packages/opencode/dist/*.tar.gz packages/opencode/dist/*.zip \
  packages/opencode/dist/SHA256SUMS

Archive names must be opencode-<target>.<ext> — the install script builds that name to fetch. Linux targets are .tar.gz, darwin and windows are .zip, both archived from <target>/bin.

Rules that bite

  • Always include -N. install rejects a bare base (1.17.9) and rejects a -N whose tag isn't released yet, rather than guessing. Both failures surface downstream, where they fail a build instead of installing a wrong binary.
  • Every release must publish SHA256SUMS. Since v1.17.9-1, install verifies the downloaded archive against it before extracting. A release without it makes every install abort.
  • Always build opencode-linux-x64-baseline. install picks the baseline binary when the host CPU lacks AVX2; if it's missing, that install 404s.
  • Never re-point or delete a shipped tag. Consumers fetch …/replopencode/v<version>/install by tag, so retagging silently changes what already-deployed machines install for a version they already pinned.
  • An installer fix reaches consumers only through a new release. Pushing to dev updates the human convenience path and nothing else.
  • Ship glibc, not musl, unless you're deliberately targeting Alpine.

Downstream

Replo pins this fork in two places, both in the replohq/andytown repo, and both move in lockstep after the release exists: the Daytona snapshot's ARG OPENCODE_VERSION, and the sandbox-upgrader's opencode curlInstall row — which rolls the new version onto already-running machines, not just new ones. So a bad release reaches production without anyone rebuilding an image.

That half of the runbook, including how to stage a prerelease from an unmerged PR without disturbing the stable line, lives in that repo's release-opencode skill (.agents/skills/release-opencode/SKILL.md).