Add changeset driven workflow for releases

[aron-cf]

This change replaces the tag-based release process with a changesets-driven release flow. Contributors now add changesets for released behavior changes, and the release workflow turns those notes into a Version Packages pull request before publishing. Private source packages such as @cloudflare/dofs, @cloudflare/computer-rpc, and @cloudflare/computerd are versioned and get changelogs, but are not published to npm.

The computerd linux-x64 package is treated as a private Docker image context rather than an npm package. Its version is derived from @cloudflare/computerd, and the changesets version step updates pinned ghcr.io/cloudflare/computer-computerd-linux-x64:<version> references in docs and examples as part of the Version Packages pull request. The stale manual npm publish path for the linux-x64 binary has been removed.

Publishing now converges the container image before npm publish. The publish script checks the desired image tags, builds and pushes missing tags to both ghcr.io and registry.cloudflare.com, then runs changeset publish. This makes reruns safe after partial failure: existing image tags are skipped, and existing npm versions are skipped by changesets.

You can verify the tooling locally with:

node --check .github/changeset-version.mjs
node --check .github/changeset-publish.mjs
npx js-yaml .github/workflows/release.yml >/dev/null
npx biome check .
git diff --check

I also tested the versioning path with a temporary private @cloudflare/computerd changeset and confirmed that it generated a private changelog, synced the derivative image package version, and updated image pins. The temporary changeset and generated release files were removed afterward.

The follow-up before the first real release is repository configuration: npm trusted publishing must point at .github/workflows/release.yml, and the container registry secrets must be present for the image publish step.

[github-actions]

Thanks for your interest in Cloudflare Computer.

This repository does not accept unsolicited pull requests. Please use one of the accepted contribution paths instead:

• Bug reports, regressions, and fix proposals: https://github.com/cloudflare/computer/issues/new/choose
• Feature requests, enhancements, and design proposals: https://github.com/cloudflare/computer/discussions

If a maintainer asked you to open this pull request, they can add the allow-pr label and reopen it.

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/@cloudflare/computer@49

commit: 2dc96d8