feat(cli): enforce tenant client version policy - #162
Draft
cubeorgdev[bot] wants to merge 4 commits into
Draft
cubeorgdev[bot] wants to merge 4 commits into
cubeorgdev[bot] wants to merge 4 commits into
Conversation
Contributor
Author
|
This pull request was created from a Blocks session. |
cubeorgdev
Bot
force-pushed
the
feat/client-version-enforcement
branch
from
September 17, 2026 03:18
32832b0 to
26d0d75
Compare
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
1 participant
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.
Consume the control plane's exact Blue release recommendation with same-major guidance and cross-major enforcement. Same-major minor, patch, prerelease, and build differences continue with a neutral notice; cross-major differences block, invalidate incompatible cache, and offer a foreground consent-based repair while background and noninteractive paths remain non-mutating.
This is intentionally stacked on #130. Merge both PRs before deploying the control-plane capability gate; after #130 merges, retarget this PR to
main.Validation:
cargo fmt --all -- --check, strict Clippy,cargo test --workspace,cargo build --workspace, focusedgh-serviceand CLI client-version tests, and byte-identical OpenAPI copies passed. Docs validation was skipped because dependencies are not installed in the workspace; Docker E2E was not available locally.Fixes #101