Present one coherent Durable Workflow 2.0 product train

Author: durable-workflow-ops

README.md

@@ -18,7 +18,7 @@ Pin an exact release for CI, conformance, or reproducible automation:
 
 ```bash
 # Linux and macOS
-curl -fsSL https://durable-workflow.com/install.sh | VERSION=0.1.80 sh
+curl -fsSL https://durable-workflow.com/install.sh | VERSION=2.0.0-beta.3 sh
 ```
 
 ```powershell
@@ -28,7 +28,7 @@ irm https://durable-workflow.com/install.ps1 | iex
 
 ```powershell
 # Windows, exact release
-$env:VERSION = '0.1.80'
+$env:VERSION = '2.0.0-beta.3'
 irm https://durable-workflow.com/install.ps1 | iex
 ```
 
@@ -45,7 +45,7 @@ downloaded binary and `SHA256SUMS` before installation.
 Or download a native binary directly from the [releases
 page](https://github.com/durable-workflow/cli/releases). The current
 supported exact release in these examples is
-[`0.1.80`](https://github.com/durable-workflow/cli/releases/tag/0.1.80).
+[`2.0.0-beta.3`](https://github.com/durable-workflow/cli/releases/tag/2.0.0-beta.3).
 Available assets:
 `dw-linux-x86_64`, `dw-linux-aarch64`,
 `dw-macos-aarch64`, `dw-windows-x86_64.exe`.
@@ -129,25 +129,25 @@ asset, including `SHA256SUMS`, the installer scripts, and the generated
 Homebrew formula, so operators can verify both checksum integrity and GitHub
 Actions build provenance with `gh attestation verify` or the release-bundled
 `verify-release.sh --attest` helper. These attestations are the current
-machine-verifiable provenance mechanism for the 0.1.x line. The one-line
+machine-verifiable provenance mechanism for the 2.0 line. The one-line
 installers keep checksum verification as the baseline and add attestation
 verification when `DURABLE_WORKFLOW_INSTALL_VERIFY_ATTESTATIONS=1` is set.
 
 Native binaries and PHARs are not currently code-signed or notarized. Treat the
 GitHub release tag, artifact attestations, and `SHA256SUMS` as the current
 provenance boundary. Signing and notarization are explicitly out of scope for
-the 0.1.x line; see [`docs/distribution.md`](docs/distribution.md) for the
+the 2.0 line; see [`docs/distribution.md`](docs/distribution.md) for the
 rationale and the conditions under which that decision would be revisited.
 
 `dw` does not auto-update itself; the explicit `dw upgrade` command is the
 only update path for standalone binary installs, and it never runs
 unsolicited. The standalone installer and direct GitHub release assets are the
 public release channels for CI and conformance jobs that only need the `dw`
 binary. Composer package metadata is not a supported public CLI distribution
-channel for the 0.1.x line. The CLI also does not collect telemetry — there is
+channel for the 2.0 line. The CLI also does not collect telemetry — there is
 no background network traffic beyond commands that explicitly contact the
 configured Durable Workflow server. Telemetry is permanently out of scope for
-the 0.1.x line.
+the 2.0 line.
 
 The PHAR is a reproducible build: given the same tag and the
 `SOURCE_DATE_EPOCH` recorded by the release workflow, locally rebuilding from
@@ -324,7 +324,8 @@ policy, worker status, search attribute type, and local dev database driver.
 
 ## Compatibility
 
-CLI version 0.1.x is compatible with servers that advertise
+CLI version `2.0.0-beta.3` is the CLI member of the supported Durable Workflow
+`2.0.0-beta.3` product train. It is compatible with servers that advertise
 `control_plane.version: "2"`,
 `control_plane.request_contract.schema: durable-workflow.v2.control-plane-request.contract`
 version `1`, and a `client_compatibility.clients.cli.supported_versions`
@@ -341,7 +342,7 @@ names the CLI version, server version, compatibility window, and next step:
 
 ```bash
 $ dw workflow:list
-Server compatibility error: refusing before the requested operation because dw 0.1.73 cannot safely interoperate with server 0.2.221. Compatibility window: cli >=0.1,<1.0; control-plane version 2; worker protocol same-major <= 1.0. Next step: Upgrade dw, pin dw to a supported release, or connect to a compatible server. Detail: Server compatibility error: missing control_plane.request_contract; expected durable-workflow.v2.control-plane-request.contract v1.
+Server compatibility error: refusing before the requested operation because dw 2.0.0-beta.3 cannot safely interoperate with server 2.0.0-beta.3. Compatibility window: cli >=2.0.0-beta.3,<2.0.0-beta.4; control-plane version 2; worker protocol same-major <= 1.0. Next step: Upgrade dw, pin dw to a supported release, or connect to a compatible server. Detail: Server compatibility error: missing control_plane.request_contract; expected durable-workflow.v2.control-plane-request.contract v1.
 Next steps:
   - Upgrade dw, pin dw to a supported release, or connect to a compatible server.
     Try: dw doctor --output=json
@@ -354,9 +355,9 @@ object for automation:
 {
   "exit_code": 8,
   "compatibility": {
-    "cli_version": "0.1.73",
-    "server_version": "0.2.221",
-    "compatibility_window": "cli >=0.1,<1.0; control-plane version 2; worker protocol same-major <= 1.0",
+    "cli_version": "2.0.0-beta.3",
+    "server_version": "2.0.0-beta.3",
+    "compatibility_window": "cli >=2.0.0-beta.3,<2.0.0-beta.4; control-plane version 2; worker protocol same-major <= 1.0",
     "next_step": "Upgrade dw, pin dw to a supported release, or connect to a compatible server.",
     "detail": "Server compatibility error: missing control_plane.request_contract; expected durable-workflow.v2.control-plane-request.contract v1."
   }

docs/distribution.md

@@ -2,7 +2,7 @@
 
 This document describes how `dw` is distributed, how operators verify the
 artifacts they install, and which optional distribution-hardening surfaces
-are deliberately out of scope for the 0.1.x line.
+are deliberately out of scope for the 2.0 line.
 
 It is the canonical reference for security-conscious users who need to
 answer "is this binary the one the project built?" and "what does this CLI
@@ -28,16 +28,16 @@ and refuse to proceed when the checksum does not match.
 For exact-version automation, set `VERSION` to the release tag:
 
 ```bash
-curl -fsSL https://durable-workflow.com/install.sh | VERSION=0.1.80 sh
+curl -fsSL https://durable-workflow.com/install.sh | VERSION=2.0.0-beta.3 sh
 ```
 
-Release `0.1.80` is available from the GitHub release page at
-<https://github.com/durable-workflow/cli/releases/tag/0.1.80>. Replace the
+Release `2.0.0-beta.3` is available from the GitHub release page at
+<https://github.com/durable-workflow/cli/releases/tag/2.0.0-beta.3>. Replace the
 tag when pinning a newer release.
 
 ## Provenance boundary
 
-The provenance boundary for the 0.1.x line is:
+The provenance boundary for the 2.0 line is:
 
 1. **The git tag** — every release is built from a tag pushed to
    `durable-workflow/cli`. The release workflow runs only on
@@ -73,7 +73,7 @@ is pinned to the same tag as the binaries it checks.
 
 ## Code signing and notarization
 
-**Decision: explicitly out of scope for the 0.1.x line. GitHub artifact
+**Decision: explicitly out of scope for the 2.0 line. GitHub artifact
 attestations are the primary provenance mechanism.**
 
 ### Why
@@ -86,7 +86,7 @@ that pass Apple Notary Service review or carry an Authenticode signature
 trusted by SmartScreen. Acquiring those identities, holding the signing
 keys correctly, and integrating them into a hosted release workflow is a
 distinct piece of operational work that we have intentionally not taken
-on for the 0.1.x line — it would not strengthen the cryptographic
+on for the 2.0 line — it would not strengthen the cryptographic
 provenance of the binary, only its handling by the OS-level publisher
 trust UX.
 
@@ -129,7 +129,7 @@ This decision is reviewable when one of the following becomes true:
 ## Telemetry
 
 **Decision: permanently out of scope. The CLI does not collect telemetry
-and will not gain a telemetry surface in the 0.1.x line.**
+and will not gain a telemetry surface in the 2.0 line.**
 
 ### Behavior contract
 
@@ -162,7 +162,7 @@ assertion is to never ship a telemetry surface at all.
 
 ### What would change this
 
-This decision is fixed for the 0.1.x line. Any future telemetry surface
+This decision is fixed for the 2.0 line. Any future telemetry surface
 would be opt-in by default, would be documented here before it shipped,
 and would be subject to the same provenance and verification expectations
 as the rest of the binary.
@@ -178,7 +178,7 @@ binary. Behavior:
   proceed if checksum verification fails, and refuses to overwrite
   Composer-managed PHAR installs and Homebrew-managed binaries because
   the package manager owns those install paths. Composer package metadata
-  is not a supported public CLI distribution channel for the 0.1.x line;
+  is not a supported public CLI distribution channel for the 2.0 line;
   use the exact-version installer or direct release assets for public,
   source-free automation.
 - Flags: `--version=<tag>` for a specific release, `--dry-run` to print
@@ -296,6 +296,8 @@ Before promoting `dw` into a production runbook:
 
 ## Change history
 
+- 2.0.0-beta.3 — Joined the synchronized Durable Workflow 2.0 product
+  train and retained the established distribution and verification policy.
 - 0.1.x — Initial distribution policy. Signing/notarization out of scope,
   telemetry permanently out of scope, reproducible-build contract
   established with `verify-reproducible-build.sh`.

scripts/generate-build-info.php

@@ -51,7 +51,7 @@
     $version = $normalizeVersion($env('GITHUB_REF_NAME'));
 }
 $version ??= $normalizeVersion($git('describe --tags --exact-match'));
-$version ??= '0.1.0-dev';
+$version ??= '2.0.0-beta.3-dev';
 
 $commit = $env('DW_CLI_COMMIT') ?? $env('GITHUB_SHA') ?? $git('rev-parse HEAD') ?? 'unknown';
 

src/BuildInfo.php

@@ -6,7 +6,7 @@
 
 final class BuildInfo
 {
-    private const FALLBACK_VERSION = '0.1.0-dev';
+    private const FALLBACK_VERSION = '2.0.0-beta.3-dev';
 
     public static function consoleVersion(): string
     {

src/Commands/UpgradeCommand.php

@@ -53,7 +53,7 @@ protected function configure(): void
 <comment>Examples:</comment>
 
   <info>dw upgrade</info>
-    <info>dw upgrade --tag=0.1.5</info>
+    <info>dw upgrade --tag=2.0.0-beta.3</info>
   <info>dw upgrade --dry-run</info>
   <info>dw upgrade --output=json</info>
 HELP)
@@ -304,8 +304,8 @@ private function versionsMatch(string $current, string $target): bool
     {
         $normalize = static function (string $value): string {
             $value = trim($value);
-            // BuildInfo::version() may return "0.1.5-dev" or "0.1.5" or fallback
-            // "0.1.0-dev"; only compare the core semver head for the noop check.
+            // BuildInfo::version() may include a development suffix; compare
+            // only the core semver head for the noop check.
             if (preg_match('/^\d+\.\d+\.\d+(?:-[0-9A-Za-z.-]+)?/', ltrim($value, 'v'), $m)) {
                 return $m[0];
             }

src/Support/CompatibilityDiagnostics.php

@@ -434,7 +434,7 @@ private static function matchesVersionConstraint(string $version, string $constr
 
             $matches = true;
             foreach ($requirements as $requirement) {
-                if (! self::matchesSingleRequirement($versionParts, $requirement)) {
+                if (! self::matchesSingleRequirement($version, $versionParts, $requirement)) {
                     $matches = false;
                     break;
                 }
@@ -451,7 +451,7 @@ private static function matchesVersionConstraint(string $version, string $constr
     /**
      * @param  array{0: int, 1: int, 2: int}  $versionParts
      */
-    private static function matchesSingleRequirement(array $versionParts, string $requirement): bool
+    private static function matchesSingleRequirement(string $version, array $versionParts, string $requirement): bool
     {
         if ($requirement === '*' || $requirement === 'x') {
             return true;
@@ -466,7 +466,7 @@ private static function matchesSingleRequirement(array $versionParts, string $re
             return $versionParts[0] === (int) $matches[1];
         }
 
-        if (preg_match('/^(<=|>=|<|>|=)?\\s*v?(\\d+)(?:\\.(\\d+))?(?:\\.(\\d+))?/', $requirement, $matches) !== 1) {
+        if (preg_match('/^(<=|>=|<|>|=)?\\s*v?(\\d+)(?:\\.(\\d+))?(?:\\.(\\d+))?((?:-[0-9A-Za-z][0-9A-Za-z.-]*)?)$/', $requirement, $matches) !== 1) {
             return false;
         }
 
@@ -476,6 +476,13 @@ private static function matchesSingleRequirement(array $versionParts, string $re
             isset($matches[3]) && $matches[3] !== '' ? (int) $matches[3] : 0,
             isset($matches[4]) && $matches[4] !== '' ? (int) $matches[4] : 0,
         ];
+        $requiredVersion = implode('.', $requiredParts).($matches[5] ?? '');
+        $normalizedVersion = ltrim(trim($version), 'v');
+
+        if (($matches[5] ?? '') !== '' || str_contains($normalizedVersion, '-')) {
+            return version_compare($normalizedVersion, $requiredVersion, $operator);
+        }
+
         $comparison = self::compareVersionParts($versionParts, $requiredParts);
 
         return match ($operator) {

tests/Support/CompatibilityDiagnosticsProductTrainTest.php

@@ -0,0 +1,35 @@
+<?php
+
+declare(strict_types=1);
+
+namespace Tests\Support;
+
+use DurableWorkflow\Cli\Support\CompatibilityDiagnostics;
+use PHPUnit\Framework\TestCase;
+
+final class CompatibilityDiagnosticsProductTrainTest extends TestCase
+{
+    /**
+     * @return array<string, mixed>
+     */
+    private function clusterInfo(string $constraint): array
+    {
+        return [
+            'client_compatibility' => [
+                'clients' => [
+                    'cli' => ['supported_versions' => $constraint],
+                ],
+            ],
+        ];
+    }
+
+    public function testProductTrainPrereleaseFloorRejectsEarlierBeta(): void
+    {
+        $clusterInfo = $this->clusterInfo('>=2.0.0-beta.3,<2.0.0-beta.4');
+
+        self::assertFalse(CompatibilityDiagnostics::cliVersionIsSupported($clusterInfo, '2.0.0-beta.1'));
+        self::assertTrue(CompatibilityDiagnostics::cliVersionIsSupported($clusterInfo, '2.0.0-beta.3'));
+        self::assertFalse(CompatibilityDiagnostics::cliVersionIsSupported($clusterInfo, '2.0.0-beta.4'));
+        self::assertFalse(CompatibilityDiagnostics::cliVersionIsSupported($clusterInfo, '2.0.0'));
+    }
+}