dev: prepare CI for v2 #5423
Merged
dev: prepare CI for v2 #5423
Conversation
This file contains 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.
Most feedback about go1.24/golangci-lint v1.64 is done, so it's time to move forward.
Instead of creating a branch
v2, we will use a branchmain.There are several advantages:
master, we will just switch the default branchmainis now standard: this is the git and GitHub default.masteris still the default, so we can release v1 bug fixes.Note: the branch
masterwill not be deleted to avoid breaking old GitHub actions, I will just create a ruleset that blocks any updates of this branch.The PR mainly disabled the publication of the doc for the branch
main, and updated the documentation.I will merge the other PRs after the merge of this one.