[rmcdaniel]

Chart 1.6.0 makes native Server 3.8.0 the default image. The chart still packages one image; appVersion, values.yaml, README and Chart annotations follow resources/release/source-release.json (helm_chart.version 1.6.0, app_version 3.8.0).

Upgrade notes (docs/UPGRADING.md):

• Every backend needs an explicit native schema upgrade (SQLite 11→12, PostgreSQL 12→13, MariaDB 12→13, MySQL 13→14). The step only creates the empty dw_task_queue_pauses table and takes seconds. Scale to zero, back up, helm upgrade with native.schemaUpgrade.enabled=true, scale up.
• Rolling back to 3.7.x requires the backup: 3.7.0 refuses with native_schema_newer_than_binary.
• From 3.5.x/3.6.x on MySQL, the same schema-upgrade run includes the 1.5.0 JSON rebuild.
• MySQL prepared-statement budget: 4 connections × 200 per node against max_prepared_stmt_count (about 20 nodes at the default), or lower DW_NATIVE_DB_STATEMENT_CACHE_CAPACITY via config.extraEnv.

These match docs/releases/3.8.0.md (#1179). Server 3.8.0's images are published and qualified: index sha256:7988a235… (native-release run 43323617904; image parity 43325373740 and published Compose 43325378480 passed), and aliases were promoted in run 43327909048.

Local: node scripts/ci/sync-source-release.mjs --check passes and scripts/ci/test_helm_chart_release.py gives 30 OK. test-source-release.mjs test 3 needs php, which lab4 lacks; it fails identically on main, and CI runs it.

After merge: Helm Chart Release publishes 1.6.0 to OCI, then docs stable-releases.json gets the helm_chart block.

🤖 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

[rmcdaniel]

Security: PASS (head 257d0af5, CI 19 pass / 8 skipping).

• Version alignment: chart 1.6.0, appVersion: "3.8.0", values.yaml image.tag: "3.8.0", the README tag, the Artifact Hub image-reference, and source-release.json (helm_chart 1.6.0 / 3.8.0) are all consistent.
• The default image resolves to the qualified build. I just read docker.io/durableworkflow/server:3.8.0 live: it's index sha256:7988a23525d9e50e997a9f6f02e801300ed4f626de3cf6977033657ae7e9f58e, the index General qualified (parity 43325373740, Compose 43325378480) and promoted (43327909048).
• UPGRADING: the schema upgrade covers all four backends, creates one empty table and takes seconds. Rollback means restoring the backup. A 3.7.0 binary refuses the newer schema with native_schema_newer_than_binary, which fails closed. The MySQL max_prepared_stmt_count budget and the DW_NATIVE_DB_STATEMENT_CACHE_CAPACITY knob are documented. The Artifact Hub changelog entries match.

Recommended for the docs read-back after the chart publishes, not blocking: the default pins by tag, which the registry can move, while the chart already supports image.digest with precedence. Add the 3.8.0 index digest above to UPGRADING (or the README) as the value change-controlled installs should set in image.digest, next to the published OCI chart digest. Then operators can pin exactly what was qualified.