Skip to content

Prepare Chart 3.0.0 for native Server 3.12.0 - #1228

Merged
rmcdaniel merged 1 commit into
mainfrom
release/chart-3.0.0
Nov 17, 2026
Merged

rmcdaniel merged 1 commit into
mainfrom
release/chart-3.0.0

Conversation

@rmcdaniel

Copy link
Copy Markdown
Member

Chart 3.0.0 advances the default native Server image from 3.11.0 to the published and promoted 3.12.0 (durableworkflow/server:3.12.0 / ghcr.io/durable-workflow/server:3.12.0, index sha256:33c7ec1d61dbbdf5c1c2248da609208bdaa8a0f8d25f3f016686c486fc7ed7f8, source da655a85). This is a chart major under the chart's own semver rule in docs/UPGRADING.md: the new default requires operator action on every backend.

Refs #1227

Operator impact

  • Explicit additive schema step on every backend: SQLite 14→15, PostgreSQL 15→16, MariaDB 15→16, MySQL 16→17. Startup never upgrades; a 3.12.0 pod on the older schema refuses with native_schema_upgrade_required and stays unready.
  • Stop every replica, back up the database and every external-payload root, run schema-upgrade once (opt-in hook or manual Job), then restart on 3.12.0.
  • After the step, 3.11.x refuses the database with native_schema_newer_than_binary, so rollback requires the pre-upgrade backup. Before the step, rolling back to Chart 2.1.0 is an ordinary Helm rollback.
  • Keep every retained external-payload root mounted (native.storage.existingClaim, or server.extraVolumes/server.extraVolumeMounts) until its objects are reclaimed.
  • Values keys are unchanged; 2.x values files work as they are. Templates and runtime code are unchanged.

Change

Mirrors the Chart 2.1.0 change (#1219), and documents the major the same way Chart 2.0.0 did. The same five files change: the authoritative resources/release/source-release.json record, the generated Chart.yaml version/appVersion/image reference, values.yaml and README defaults (written by sync-source-release.mjs --write), the Artifact Hub changelog, and a new Chart 3.0.0 / Server 3.12.0 section in docs/UPGRADING.md. PHP Server stays 2.11.8. No CLI, Waterline or Cloud adoption, and no #980 or #1204 resolution, is inferred.

Validation (local)

  • node scripts/ci/sync-source-release.mjs --check: synchronized; node --test scripts/ci/test-source-release.mjs: 3/3 pass (in a PHP+git container).
  • scripts/ci/test_helm_chart_release.py: 30/30 pass; helm_chart_release.py check-version --base-ref origin/main: 2.1.0 → 3.0.0.
  • Helm v3.16.2 (CI version): helm lint on the default and all six ci/*-values.yaml fixtures pass; every fixture renders, and the native fixtures render server:3.12.0.
  • test_database_tls_chart.py (4) and test_helm_runtime_modes.py (20): pass.
  • git diff --check: clean.

Not run locally: kubeconform and the chart-testing kind install. These run in hosted CI. OCI publication and anonymous install verification follow merge through the chart release workflow.

🤖 Generated with Claude Code

Advance the chart default to native Server 3.12.0. The release requires an
explicit schema upgrade on every backend, so the chart major advances under
the chart's semver rules. Values keys and templates are unchanged.

Refs #1227

Co-Authored-By: Claude Opus 5.5 <[email protected]>
@rmcdaniel

Copy link
Copy Markdown
Member Author

General review of head fe133f04: PASS. The five files match the #1219 pattern; version 2.1.0→3.0.0 and appVersion/tag→3.12.0 are synchronized by sync-source-release.mjs. The new UPGRADING section matches docs/releases/3.12.0.md:

  • the schema table and the explicit schema-upgrade with replicas stopped;
  • backup of the database and every payload root;
  • a skipped step leaving pods unready (native_schema_upgrade_required, correct on MySQL 16 since Name the upgrade step for MySQL schema 16 #1226 is in the 3.12.0 tag) while existing pods keep serving;
  • ordinary rollback before the step, backup-restore rollback after it;
  • the retained-root mounting guidance.

Major per this guide's semver rule, as recorded in #1227. Merging through the queue once hosted checks pass.

@sonarqubecloud

Copy link
Copy Markdown

@rmcdaniel
rmcdaniel added this pull request to the merge queue Nov 17, 2026
Merged via the queue into main with commit 13ad454 Nov 17, 2026
27 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant