Repository navigation
Follow jumpbox default branch and branch-neutral APT key URLs - #699
Merged
Merged
Conversation
Contributor
|
No actionable comments were generated in the recent review. WalkthroughThe Ubuntu APT and Fedora/RHEL YUM signing-key URLs in the README now use Merge Risk:
|
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 read-only jumpbox Git source will follow its repository's default branch. APT and RPM signing-key URLs use
HEAD, which works before and after the APT repository rename.Validation:
git diff --checkpassed. Parsed before/after comparisons confirm only the intended Git branch selectors changed. Modern local strict pipeline validation reports the same pre-existing template/legacy-schema errors before and after this patch; it does not establish runtime compatibility. HTTP downloads of both APT/RPM key URLs throughHEADreturned HTTP 200 and matched the correspondingmasterbytes.Default-following consumer changes can be merged and, where deployed, applied by their operators before the target rename.
Concourse Git resource contract: a read-only source can omit
branch; a source used forputneeds an explicit branch.This PR changes checked-in files only. Deployed pipeline reconfiguration and runtime checks remain operator-owned; no Concourse pipelines or jobs were modified, paused, unpaused, or triggered for this work.
Cutover plans:
Shared community configuration (draft): cloudfoundry/community#1682