Repository navigation
Prepare Chart 3.0.0 for native Server 3.12.0 - #1228
Merged
Merged
Conversation
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]>
Member
Author
|
General review of head
Major per this guide's semver rule, as recorded in #1227. Merging through the queue once hosted checks pass. |
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.



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, indexsha256:33c7ec1d61dbbdf5c1c2248da609208bdaa8a0f8d25f3f016686c486fc7ed7f8, sourceda655a85). This is a chart major under the chart's own semver rule indocs/UPGRADING.md: the new default requires operator action on every backend.Refs #1227
Operator impact
native_schema_upgrade_requiredand stays unready.schema-upgradeonce (opt-in hook or manual Job), then restart on 3.12.0.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.native.storage.existingClaim, orserver.extraVolumes/server.extraVolumeMounts) until its objects are reclaimed.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.jsonrecord, the generatedChart.yamlversion/appVersion/image reference,values.yamland README defaults (written bysync-source-release.mjs --write), the Artifact Hub changelog, and a newChart 3.0.0 / Server 3.12.0section indocs/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 linton the default and all sixci/*-values.yamlfixtures pass; every fixture renders, and the native fixtures renderserver:3.12.0.test_database_tls_chart.py(4) andtest_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