Repository navigation
fix: offer the maintained CLI through release defaults - #307
Merged
Merged
Conversation
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.
Prepare Server v1.6.536 with maintained CLI v0.6.18 release defaults and advertised version. Use the official producer platform-before-version asset layout, without publication aliases. The optional PASTURESTACK_CLI_RELEASE_BASE_URL derives all three CLI URLs from the effective CATTLE_RANCHER_CLI_VERSION. Without the new base, retain the historical RC16 layout. Explicit DEFAULT_CATTLE/CATTLE URLs and saved database URLs remain authoritative. A modern CLI-only base does not introduce an active compose version override. No SQL migration, runtime binary patch, authentication, backend API, firewall or volume change; Web189 and Engine349 identities remain unchanged. Seven focused Linux Bash default/version/operator/legacy/modern-only cases passed with zero skips on the exact reviewed source fixture; see cli536-bash-contract-native-v3.json. The earlier 4-case and 7-case receipts remain unmodified. The 38 packaging source contracts previously passed and were not rerun for the compose-only branch refinement. All normal strict required CodeQL, source gates and final-image publication checks remain mandatory. Do not merge or publish before the immutable official CLI018 release, checksum readback and native Full/absent-policy legacy/Closed command acceptance. Server535 remains published unchanged.