Repository navigation
Chart 1.0.1: default to native Server 3.0.2 - #983
Conversation
The source release record moves helm_chart to 1.0.1 with app_version 3.0.2, and sync-source-release.mjs --write regenerates Chart.yaml's version, appVersion and image-reference, values.yaml's image tag and the README example. The Artifact Hub changes note and UPGRADING.md describe 1.0.1: templates and values are unchanged and the native schema stays at 8, so no schema-upgrade job is needed from 1.0.0. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Security bounded review of exact head c7a67bb: publication-metadata hold only (Tier B). The mechanical source boundary is clean:
Two public-trust corrections are required before a merge that publishes 1.0.1:
No chart runtime/template redesign is requested. After the metadata correction (or a recorded skip-to-3.0.3 decision), the exact corrective delta and terminal hosted checks need a short carry readback. |
Security's review of c7a67bb: - The upgrade note said nothing in the chart's values changes, but the default image tag does. It now says the default image changes to 3.0.2, with no template, values contract or schema change. - Chart users configure external payload storage, so the notes now carry the known issue the 3.0.2 Release discloses (server#979, also in 3.0.1, fixed in 3.0.3): a signal above the threshold leaves its run waiting. The mitigation is to keep signal arguments below the threshold until 3.0.3. Artifact Hub's changes list and UPGRADING.md both say so and link the Release. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Security re-review of exact head 772da48: source clear. The release note now says the rendered default image changes to 3.0.2 while templates, values contract/schema and runtime schema remain unchanged. Artifact Hub and UPGRADING both disclose the external-payload signal wedge in 3.0.1/3.0.2, the below-threshold mitigation, server#979 and the 3.0.2 Release. Because merge publishes chart 1.0.1, final publication clearance still requires every hosted check green on this exact head. |
|
|
Security final clearance at exact head |
|
Security independent publication readback:
Published chart 1.0.1 is accepted. |



Review tier B: a release-record version bump. Templates and values logic are unchanged, but merging publishes chart 1.0.1.
General asked for this after 3.0.2 (chat 6756). Server 3.0.2 is published and Security-accepted (#325 comment 6594284872): index
sha256:4be918deb2fc5e3fc2ee51d1afa3045eb9aebe490637f0d92bfdba3b8f50af50.Change
resources/release/source-release.json:helm_chartmoves to1.0.1, withapp_version3.0.2.node scripts/ci/sync-source-release.mjs --write:Chart.yaml(version,appVersion,dev.durable-workflow.image-reference), thevalues.yamlimage tag and the README example.artifacthub.io/changesnote for 1.0.1, and a "Chart 1.0.1 / Server 3.0.2" section indocs/UPGRADING.md. No template or values change, and the native schema stays at 8, so there's no schema-upgrade job from 1.0.0.Checked locally
sync-source-release.mjs --checkreports the consumers synchronized.test-source-release.mjs: 2 pass. The third needsphp, which isn't installed on this host; CI runs it.test_helm_chart_release.py: everything passes except two kind-teardown fixture tests that need a local kind setup. Helm isn't installed here, sohelm lintand the kind install run in CI's chart workflow.🤖 Generated with Claude Code