Repository navigation
ci: run CI on the next branch; document next for the upcoming major - #2028
Merged
Merged
Conversation
- ci.yml triggers on pushes and PRs to next as well as main. Cache saving stays main-only: the repo is at its cache quota, and next falls back to main's caches. - releasing.md: what goes on next, merging main into it, landing it with a merge commit so per-PR history and release notes survive, and not tagging it by accident. - issue-linking.md: closing keywords never fire for PRs into next; carry them into the next -> main PR body.
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
Sets up
nextas the long-lived branch for the next major version (index format changes and other reindex-requiring work), whilemainkeeps shipping patch and minor releases.ci.ymlnow triggers on pushes and PRs tonextas well asmain. Cache saving stays main-only: the repo is already at its 10 GB Actions cache quota, and runs onnextrestore from main's caches.releasing.mdgains a section onnext: what goes there, mergingmaininto it regularly, landing it with a merge commit (not squash/rebase) so per-PR history survives, and not tagging it by accident (anyvX.Y.Ztag triggers a release).issue-linking.md: closing keywords never fire for PRs intonext, including whennextlater merges intomain; carry them into thenext→mainPR body.Release notes
GitHub's generated notes include PRs merged into a non-default branch as long as their commits fall in the tag range. Checked with the
generate-notespreview API for v4.1.6 → v4.2.0: #1755 (merged into a feature branch, notmain) is listed individually alongside its parent #1752. So no manual release notes are needed whennextlands, provided it lands with a merge commit and its PRs carry labels.nextalready exists at this PR's commit, so CI applies to PRs intonextimmediately; merging this PR and later mergingmainintonextreconciles cleanly.