Repository navigation
Select Server 3.7.0 and chart 1.5.0; MySQL JSON schema upgrade - #516
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
rmcdaniel
marked this pull request as ready for review
November 12, 2026 12:22
|
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.



Selects native Server 3.7.0 and Helm chart 1.5.0, modeled on #514.
Docs
docs/deployment.md: new section Upgrading to Server 3.7.0 (#native-schema-upgrade-3-7) above the 3.5.0 section. It covers the MySQL-only schema upgrade from 12 to 13. MySQL's 75jsoncolumns in 36 tables becomeLONGTEXT(utf8mb4_bin) with ajson_validcheck. The Server is down for the whole upgrade, about 2 minutes per million history rows, and an interrupted upgrade resumes table by table. Rolling back needs the backup (native_schema_newer_than_binary). The section gives the Compose steps (schema-upgradeprints12 → 13). MariaDB and PostgreSQL stay at 12 and SQLite at 11, so they only change the image. From 3.4.x or earlier, the 3.5.0 step still applies. The worker protocol stays at1.20and the control plane at2(checked in the server source at the 3.7.0 tag). One paragraph covers the native redrive changes (#980): memos and search attributes set at start carry over, anddescribereportsactions.can_redriveandactions.redrive_blocked_reason.docs/deployment.md: a Chart 1.5.0 passage in the Helm section links to…UPGRADING.md#chart-150--server-370-nativeand#native-schema-upgrade-3-7.docs/failures-and-recovery.md: native redrive no longer says it only applies the rules from before 2.18.0. It now notes what 3.7.0 adds and that the remaining work is tracked in server#980. This mirrors Select native Server 3.6.0 and chart 1.4.0 #514's monitoring.md change.source-hashes.json.Release metadata
static/stable-releases.json: server3.7.0, helm-chart1.5.0,app_version3.7.0.tests/kubernetes-workers/artifacts.json:durableworkflow/server@sha256:27ca9a9156c9e4b489de770b4d5abc10f5ba9fc6da97134d26432fcaabdf37fb, the 3.7.0 image index digest. Select native Server 3.6.0 and chart 1.4.0 #514 also used the index digest for 3.6.0.Pending (do not merge yet):
helm_chart.oci_manifest_digest,package_digest,source_commitandqualification_urlare set toTODO-GENERAL. They get filled in after chart 1.5.0 (server#1167) publishes. Until then,check-helm-chart-pairing.test.jsandnpm testfail with "must be a SHA256 digest". With well-formed placeholder values, both pass.Checks:
check-doc-translations.jspasses, including theDOCS_TRANSLATION_BASEupdate comparison. The install-sdk, installer-source, server-config-reference, local-search, translation-updates and localized-links checks pass, as does the public-boundary script and pytest.npm testpasses with placeholder digests. The fulldocusaurus buildwas not run.🤖 Generated with Claude Code