Fix compatibility manifests for partial Server releases - #500
Merged
Merged
Conversation
longquanzheng
marked this pull request as ready for review
September 18, 2026 04:12
longquanzheng
enabled auto-merge (squash)
September 18, 2026 04:13
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.
Server v0.10.0 shipped without its compatibility manifest because the changed-component workflow required every SDK to be released together. Four unchanged SDKs were skipped, so the manifest job was skipped and the final gate still reported success.
Require a manifest for every selected Server release and fail the final gate when it is absent. Preflight declarations before creating component tags. Allow declarations to pin each component's actual released version, validate protocol intervals against each tagged source, and verify client/Server protocol overlap. Add the v0.10.0 declaration using v0.10.0 Server/CLI/Go SDK and v0.9.0 for the other SDKs. Existing manifests remain immutable; v0.9.0 output is byte-identical.
Validation:
make release-tooling-test(20 tests),make ci-runner-check,make copyright-check, and actionlint passed. Generated v0.10.0 with--verify-releases, checking GitHub release targets, CLI asset digests, and the published Docker image digest. Manifest SHA-256:dec8dd6d9a3734e8afbf14acfb740830dc63c361d4957d1fa9f4810a61f311d9.Documentation: CONTRIBUTING explains partial releases and immutable backfills. UI/UX: N/A; release tooling only.