Skip to content

Fix compatibility manifests for partial Server releases - #500

Merged
longquanzheng merged 2 commits into
mainfrom
codex/partial-release-manifest
Sep 18, 2026
Merged

longquanzheng merged 2 commits into
mainfrom
codex/partial-release-manifest

Conversation

@longquanzheng

Copy link
Copy Markdown
Contributor

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.

@longquanzheng
longquanzheng marked this pull request as ready for review September 18, 2026 04:12
@longquanzheng
longquanzheng enabled auto-merge (squash) September 18, 2026 04:13
@longquanzheng
longquanzheng merged commit 5b53541 into main Sep 18, 2026
5 checks passed
@longquanzheng
longquanzheng deleted the codex/partial-release-manifest branch September 18, 2026 04:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant