Repository navigation
Expose the published Helm chart pairing and upgrade guidance - #378
Merged
Merged
Conversation
rmcdaniel
marked this pull request as ready for review
October 23, 2026 09:58
|
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.
The compatibility tuple omits the Helm chart, and deployment leaves its version unpinned. All eight locales now expose the verified chart 0.2.3 / Server 2.10.1 pairing from the existing release metadata, pin the install command, link immutable source and UPGRADING guidance, and explain custom image overrides and the historical 0.2.2 version-policy exception.
Refs #346 and the published OCI/package verification. Metadata records both digests and exact source identity. The renderer uses generated tokens and artifact surfaces, and the normal build rejects a selected Server/appVersion mismatch or missing digest evidence. All seven existing component versions stay unchanged; no newer tuple, runtime adoption or fresh cluster-install result is claimed.
Validation: three named node:test checks cover mismatch/unqualified metadata and URL expansion; all seven reviewed-source hashes and code examples match. Exact-head documentation qualification builds all eight locales and executes the new metadata check. Normal merge d6b2d85, artifact39942081305 and actual Pages39943140320 pass. Live rows/metadata, commands and links are being verified before closure. Sonar reports zero new issues after converting the assertions to named tests.
The initial failed qualification exposed MDX URL decoding before artifact substitution. The artifact plugin now uses Docusaurus’s documented beforeDefaultRemarkPlugins hook, and a raw-URI failure/resolved-URL control is included. The failed run remains separate; the current all-locale build must pass before merge.