Cloudflare Computer Release Notes: Where to Find Official Updates

Release notes for cloudflare/computer are published exclusively on the GitHub Releases page, generated automatically via Changesets rather than stored as a static changelog in the repository.

Unlike many open-source projects that track version history in a CHANGELOG.md file, the cloudflare/computer repository uses an automated release management workflow. Understanding where to find official release notes for cloudflare/computer requires knowing how the project leverages Changesets and GitHub Releases to document changes across its multiple packages.

Where to Find Cloudflare Computer Release Notes

The canonical source for release notes is the GitHub Releases page: https://github.com/cloudflare/computer/releases. The repository does not maintain a traditional CHANGELOG.md file in the source tree. Instead, each published version's release notes appear as a markdown draft on the GitHub Releases interface, where maintainers review and publish them before they become publicly visible.

How Release Notes Are Generated

The project uses Changesets, a version management tool, to automate release documentation. The workflow defined in COLLABORATORS.md follows this four-step process:

1. Changeset creation: Developers add or update Changeset files (.changeset/*.md) when merging changes into the main branch
2. CI execution: The pipeline runs changeset version && changeset publish, which bumps package versions and creates a markdown release draft
3. Maintainer review: The draft appears on GitHub Releases for maintainers to review and edit
4. Publication: Upon release, npm packages (@cloudflare/*) receive new version tags and the notes become public

This approach ensures release notes for cloudflare/computer are always synchronized with the actual code changes and package versions deployed to the registry.

Independent Package Versioning

Cloudflare Computer is a monorepo containing multiple independently versioned packages. The release notes on GitHub aggregate changes across:

• @cloudflare/computer: The main entry point package
• @cloudflare/computerd: The daemon powering the FUSE backend
• @cloudflare/dofs: The SQLite-backed virtual filesystem layer
• @cloudflare/rpc: The Cap'n Proto (capnweb) RPC contract between the Durable Object and daemon

Each package maintains its own semantic version, and the GitHub Release reflects the collective updates across the workspace for that release cycle.

How to Check the Latest Release

To verify your installed version against the official release notes:

# Install the top-level package

npm i @cloudflare/computer

# Check the installed version

npm list @cloudflare/computer

# Example output: @cloudflare/computer@0.12.3

# View the corresponding release notes in your browser

open https://github.com/cloudflare/computer/releases/tag/v0.12.3

Replace v0.12.3 with your specific version tag to view the relevant release notes.

Key Documentation Files

Several files in the repository govern or supplement the release process:

• COLLABORATORS.md (Releases section): Documents the complete release workflow, version bumping procedures, and how to add release-note entries
• packages/computer/README.md: Entry point for the main package with installation instructions reflecting the current released version
• packages/computerd/README.md: Documentation for the FUSE backend daemon
• packages/dofs/README.md: Details on the SQLite-backed virtual filesystem layer
• packages/rpc/README.md: Specifications for the Cap'n Proto RPC contracts

Summary

• Release notes for cloudflare/computer are published on the GitHub Releases page, not as a static file in the repository
• The Changesets workflow described in COLLABORATORS.md automates version bumping and release note generation from .changeset/*.md files
• Each package in the monorepo (@cloudflare/computer, @cloudflare/computerd, @cloudflare/dofs, etc.) is versioned independently
• Release drafts are generated by the CI pipeline running changeset version && changeset publish before maintainer review
• Package-specific installation and usage details are maintained in each packages/*/README.md file

Frequently Asked Questions

Does cloudflare/computer have a CHANGELOG.md file?

No. According to the repository structure, cloudflare/computer does not include a static CHANGELOG.md file in the source tree. Release notes are generated dynamically using the Changesets tool and published exclusively on the GitHub Releases page.

How do I find the release notes for a specific version?

Navigate to https://github.com/cloudflare/computer/releases/tag/v[VERSION] replacing [VERSION] with your installed version number (for example, v0.12.3). You can verify your current version by running npm list @cloudflare/computer in your terminal.

What triggers the creation of new release notes?

New release notes are triggered when the CI pipeline detects Changeset files (.changeset/*.md) and executes changeset version && changeset publish. As documented in COLLABORATORS.md, this process automatically generates a markdown draft that maintainers review before publishing to the GitHub Releases page.

Are all packages in the monorepo released together?

While the GitHub Release aggregates changes into a single notes entry, each package (@cloudflare/computer, @cloudflare/computerd, @cloudflare/dofs, etc.) is versioned independently. The release notes specify which packages received version bumps, allowing users to identify relevant changes for specific dependencies.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}