Versioning Strategy for cloudflare/computer: Independent Semantic Versioning in an npm Workspace Monorepo

The cloudflare/computer repository implements independent semantic versioning within an npm workspace monorepo, allowing each package to maintain its own distinct version number rather than enforcing a single global version across all components.

The cloudflare/computer project is organized as a modern JavaScript monorepo using npm workspaces. This architecture necessitates a flexible versioning strategy that accommodates multiple publishable packages while allowing granular control over release cycles.

How the Monorepo Structure Influences Versioning

Unlike repositories that enforce synchronized versioning across all modules, cloudflare/computer adopts an independent versioning strategy. This approach aligns with standard npm workspace practices and enables teams to release updates to individual components without forcing unnecessary version bumps in unrelated packages.

Root Package Configuration

The root package.json serves exclusively as a workspace manifest and uses a placeholder version that does not reflect actual releases.

// package.json (root)
{
  "name": "@cloudflare/computer",
  "version": "0.0.0",
  "workspaces": [
    "packages/*"
  ]
}

This 0.0.0 placeholder indicates that the root package is not published to npm; it exists solely to coordinate dependencies and scripts across the workspace.

Individual Package Versions

Each publishable package within the packages/ directory maintains its own semantic version in its respective package.json. Current versions include pre-release identifiers indicating active development:

• packages/computerd/package.json: Version 0.1.0-alpha.1 for the CLI component
• packages/computer/package.json: Version 0.1.0-alpha.1 for the core library
• packages/dofs/package.json: Version 0.0.0 for the storage layer

Version Examples from the Source Code

The following configurations demonstrate how independent versioning is implemented across key components:

// packages/computerd/package.json
{
  "name": "@cloudflare/computerd",
  "version": "0.1.0-alpha.1",
  "description": "Cloudflare Computer daemon"
}

// packages/computer/package.json
{
  "name": "@cloudflare/computer",
  "version": "0.1.0-alpha.1",
  "description": "Core computer functionality"
}

// packages/dofs/package.json
{
  "name": "@cloudflare/dofs",
  "version": "0.0.0",
  "description": "Distributed object filesystem"
}

These version fields are managed independently, allowing computerd to advance to 0.1.0-beta.1 or 0.2.0 while dofs remains at 0.0.0 or advances on its own schedule.

Pre-Release and Stable Release Patterns

The versioning strategy for cloudflare/computer follows Semantic Versioning 2.0.0 conventions. During active development, packages use pre-release identifiers such as alpha and beta:

• 0.1.0-alpha.1 indicates an early development build
• Future stable releases will transition to standard MAJOR.MINOR.PATCH format (e.g., 1.0.0)

This pattern allows developers to publish experimental features to npm without signaling production stability, while the independent approach ensures that a stable release of one package does not require stable releases of all dependent packages simultaneously.

Benefits of Independent Versioning in cloudflare/computer

Independent versioning provides several advantages for this architecture:

• Granular release control: Updates to the CLI in computerd can ship as 0.1.0-alpha.2 without affecting the core computer library version
• Reduced version churn: Bug fixes in one package do not force version increments in stable, unchanged packages
• Clear dependency graphs: Each package explicitly declares its compatible version ranges, preventing implicit coupling between component release cycles
• Flexible maturity levels: The storage layer (dofs) can remain at 0.0.0 while the CLI advances through alpha and beta phases

Summary

• The cloudflare/computer repository uses npm workspaces to manage multiple packages within a single monorepo.
• The root package.json uses version 0.0.0 as a non-publishable workspace manifest.
• Each package in packages/ maintains its own independent semantic version (e.g., 0.1.0-alpha.1 for computerd and computer).
• Pre-release identifiers (alpha, beta) indicate development status before stable MAJOR.MINOR.PATCH releases.
• This strategy enables fine-grained publishing control and aligns with standard npm workspace best practices.

Frequently Asked Questions

Does cloudflare/computer use a single global version number?

No. Unlike some monorepos that enforce synchronized versioning, cloudflare/computer uses independent versioning where each package maintains its own version in its respective package.json file. The root package.json uses 0.0.0 strictly as a workspace placeholder and is not published.

What versioning scheme does cloudflare/computer follow?

The repository follows Semantic Versioning 2.0.0 (SemVer). Versions follow the MAJOR.MINOR.PATCH format, with additional support for pre-release identifiers such as -alpha.1 or -beta.2 during development cycles.

How are pre-release versions handled in cloudflare/computer?

Pre-release versions use hyphenated identifiers appended to the semantic version number, such as 0.1.0-alpha.1 found in packages/computerd/package.json and packages/computer/package.json. These tags signal non-production readiness and allow iterative publishing to npm before stable releases.

Where are version numbers defined in the cloudflare/computer repository?

Version numbers are defined in each package's package.json file. Key locations include the root package.json (placeholder 0.0.0), packages/computerd/package.json (0.1.0-alpha.1), packages/computer/package.json (0.1.0-alpha.1), and packages/dofs/package.json (0.0.0).

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