[rmcdaniel]

Summary

Adopts the published PHP SDK 3.11.0 (covering 3.9.5 and 3.10.0) and Workflow 2.22.0 (covering 2.21.1) in the docs. Server, Helm chart, CLI and the other SDK selections are unchanged.

• static/stable-releases.json: sdk-php 3.9.4 → 3.11.0, workflow 2.21.0 → 2.22.0, updated_at 2026-11-09.
• docs/polyglot/php.md
  • Requirements now separate the bare SDK (PHP 8.1+) from the Laravel bridge in 3.10+ (PHP 8.2+, Laravel 12.69/13.30, PHP 8.3+ for Laravel 13).
  • New section Upgrade to PHP SDK 3.10 and 3.11 covering:
    • the Laravel bridge floors and how the provider refuses unsupported platforms;
    • rolling out v2 dwphp2:sha256: condition fingerprints: upgrade the whole queue, deploy atomically and restart OPcache workers (rollback below 3.10 can fail replay);
    • stricter static credential validation;
    • 3.11 occurrence deadlines: they need native Server 3.3.0's condition_wait_occurrence_deadline, the rollout order depends on the Server, and workers must not be rolled back below 3.11 once anchored waits exist.
  • Also lists the new 3.10 APIs and documents the iterateWorkflows() / iterateWorkflowHistory() iterators. The section previously said no iterator capability was implied.
• docs/compatibility.md
  • Laravel support table: Workflow 2.22, a new PHP SDK 3.11 bridge row, and the 3.9.5 row kept as the older line.
  • Upgrade contract link now points to 2.22.0.
  • New paragraph on the SDK 3.10 bridge change.
  • New Workflow 2.22 note: no migration, same floors, embedded protocol advertises 1.22 and still accepts 1.20, the embedded runner's waiting behavior is unchanged, and rollback after the occurrence policy has been used is backup-restore only.
• docs/laravel-adoption.md: no longer says the published SDK supports Laravel 10–13. From 3.10 the bridge has the same floors as the embedded package; 3.9.x keeps its earlier contract. Adds the provider refusal.
• All seven translations (de, es, fr, ja, pt-BR, uk, zh-Hans) are updated for the three guides. Each i18n/<lang>/source-hashes.json entry for them is set to the English file's SHA-256, as the README describes.

All claims come from the GitHub release notes, the tagged CHANGELOGs and the sdk-php 3.11.0 upgrade guide.

Checks (run locally)

• npm ci --ignore-scripts, npx --no-install patch-package, then DOCS_TRANSLATION_BASE=57e32836… npm run build (the CI qualification build) in a node:24.22.1-bookworm container. Exit 0.
  • The build includes the dependency, toolchain, identity, helm-pairing, install-sdk, installer, server-config, local-search, translation-update, translation and localized-link checks, plus browser-header tests.
  • All 8 locales built, and the llms files were generated.
  • Translation result: "Translation updates match reviewed English sources for 3 changed guides in all seven other locales"; 108 guides have current hashes.
  • The only warnings were existing blog-author and truncation warnings.
• npm test (protocol specs, worker OpenAPI, protocol page, llms-full, browser headers): 17/17 pass.

🤖 Generated with Claude Code

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud