Repository navigation
Select the native tuple Server 3.5.0 and chart 1.3.0 - #503
Merged
Merged
Conversation
Pin Server 3.5.0 (tag 3.5.0 -> 1b8e9ee4, index sha256:b5776fea...) and Helm chart 1.3.0 with appVersion 3.5.0, built from chart source 66c0196c and published by Helm Chart Release run 43122786956. An anonymous GHCR read returns OCI manifest sha256:2355dba8... with one chart layer sha256:27ccf139...; the downloaded package hashes the same and carries version 1.3.0, appVersion 3.5.0 and image durableworkflow/server:3.5.0. qualification_url cites that readback on server#1149. Document the upgrade to 3.5.0: one new native-only table moves the schema from 11 to 12 on MySQL, MariaDB and PostgreSQL (10 to 11 on SQLite), with backup, an explicit schema-upgrade and restore-only rollback. Checked on lab4: 3.5.0 refuses a 3.4.0 SQLite database with native_schema_upgrade_required, schema-upgrade reports 10 -> 11, and a second run reports current. Add the chart 1.2.0 and 1.3.0 notes. Update the cluster-info example to the 3.5.0 image (sticky_execution, sticky_history_suffix, activity_workflow_continuation) from a live read, and move the Kubernetes worker-guide fixture to the 3.5.0 index. All seven translations and their source hashes are updated. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
….0-chart-1.3.0 # Conflicts: # static/stable-releases.json
rmcdaniel
marked this pull request as ready for review
November 12, 2026 01:00
|
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.
Docs adoption of native Server 3.5.0 and Helm chart 1.3.0 (step 2 of General's docs catch-up).
Change
static/stable-releases.jsonselects Server3.5.0and chart1.3.0. Thehelm_chartblock has OCI manifestsha256:2355dba8…, packagesha256:27ccf139…, source66c0196c. The qualification URL is my anonymous GHCR readback on server#1149.deployment.md: a new section, "Upgrading to Server 3.5.0":schema-upgrade, start;The existing 3.0.x → 3.3.2 section now says to use the 3.5.0 image when jumping straight there. The Helm section adds the chart 1.2.0 notes (no schema change,
preStopsleep, 70 s grace) and the chart 1.3.0 notes (schema upgrade withnative.schemaUpgrade.enabled=true).polyglot/server.md: the cluster-info example and notes move to the 3.5.0 image. They addsticky_executionandsticky_history_suffix(3.5.0) andactivity_workflow_continuation(3.4.0) underworker_protocol.server_capabilities.tests/kubernetes-workers/artifacts.jsonmoves to the 3.5.0 indexsha256:b5776fea…. Becausedeployment.mdchanged, the Kubernetes worker-guide job runs the published SDK workers against it.Checks run
native_schema_upgrade_required.schema-upgradereturned{"backend":"sqlite","from_schema_version":10,"schema_version":11,"status":"upgraded"}, then"status":"current"on a second run./api/cluster/infogave the fields used in the example. Containers and volume removed.Chart.yaml/values.yamlshow 1.3.0 / 3.5.0.check-doc-translations.jsandcheck-helm-chart-pairing.test.jspass locally.Merging this and #457 both touch
stable-releases.json(updated_atmatches). Whichever lands second gets a trivial main merge.🤖 Generated with Claude Code