Repository navigation
Configure main as the bosh-deployment default branch - #1686
Merged
Merged
Conversation
This was referenced Nov 3, 2026
Merged
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.
Set the published default branch of
bosh-deploymenttomain; its generated protection selector followsmain. Thedevelopcontribution branch and promotion process remain in place.Primary preparation PR (targets
develop): cloudfoundry/bosh-deployment#538Central cutover issue: cloudfoundry/bosh-deployment#539
Keep this PR in draft until the native rename and required operator verification are complete. Merge and normally promote the source preparation first. Read-only consumers can be staged ahead; promotion/write selectors must be applied only after
mainexists. Active consumer readiness matters independently of whether an external owner has merged its source PR. Documentation-only changes and confirmed inactive templates are non-gating.bosh-linux-stemcell-builder(ubuntu-jammy)boshcf-deployment(develop)credhubprometheus-boshreleasedocs-boshbosh-bootloaderbosh-azure-cpi-releasebosh-virtualbox-cpi-releasebosh-google-cpi-releasebosh-aws-cpi-releasebuildpacks-cibosh-alicloud-cpi-releasebosh-openstack-cpi-releasebosh-cpi-certificationbosh-vsphere-cpi-releasebosh-dns-releasebosh-docker-cpi-releasebosh-warden-cpi-releasejuicefs-releasecli-cibosh-alicloud-light-stemcell-builderbosh-disaster-recovery-acceptance-testsbosh-linux-stemcell-builder(ubuntu-noble)bosh-linux-stemcell-builder(ubuntu-resolute)The org-wide audit covered public indexed references and current consumer checkouts. Golden BBL fixtures and 2018 lab state snapshots are preserved as historical data. Existing default-following clones, explicit
develop/release pins, independent repositories and unrelated branch selectors require no source edit for this rename. Existing local checkouts still need their upstream updated normally.Validation: ownership/schema and full generated org/protection comparisons passed; only this default and its
^master$to^main$selector change. All diffs passed whitespace checks. Parsed pipeline comparisons match the intended selectors; all three maintained stemcell templates render and pass strict offline validation. Older templates retain the same baseline schema errors. The primary PR guard was checked structurally.Deployed Concourse pipelines and pause states were not changed. After merge, a successful Peribolos synchronization containing this configuration must eventually finish before everything is complete; no particular long-running/canceled run is a checklist gate.
GitHub check note: the Alicloud consumer audit fails
Dependency Audit (nancy)becausesonatype-nexus-community/nancy-github-action@v1cannot be resolved, andGo Vulnerability Checkreports Go standard-library vulnerabilities. The unmodified baseline already fails both jobs. This migration changes only two Git source branch selectors in that repo; Go source/dependencies and workflows are unchanged. The failures are documented for owner follow-up and have not been bypassed or rerun.