ci: drop v5 from release and CI branch config - #445
Merged
Conversation
5.0.0 stable shipped from main, so the v5 pre-release channel is retired. - `.releaserc.js`: remove the `v5` prerelease branch (rc / `next` channel) - `release.yml`, `ci.yml`: drop `v5` from the push and pull_request triggers - `renovate.json`: drop `v5` from `baseBranchPatterns` so Renovate stops raising PRs against a branch that is about to be deleted Prerequisite for deleting `origin/v5`, which is fully contained in main.
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.
Summary
5.0.0 stable shipped from
main(promotion merge bbd80db), so thev5pre-release channel is retired. This removes the remainingv5references from the release and CI configuration, which is a prerequisite for deletingorigin/v5— that branch is fully contained inmain.Details
{ name: 'v5', prerelease: 'rc', channel: 'next' }branch from.releaserc.jsv5from the push trigger inrelease.ymlv5from thepull_requesttrigger inci.ymlv5frombaseBranchPatternsinrenovate.json, so Renovate stops raising PRs against a branch that is about to be deleted (this is what produced chore(deps): lock file maintenance #444)Follow-up
Once this merges,
origin/v5can be deleted. #431 has already been retargeted tomainso it won't be auto-closed by the deletion; #444 will auto-close with the branch, and Renovate will re-raise lock file maintenance againstmainon its next run.