Update CI & release checklist for release branch #3312
Merged
Conversation
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
github-actions
bot
added
the
needs release notes
d-v-b
approved these changes
Jul 31, 2025
dstansby
removed
the
needs release notes
meeseeksmachine
pushed a commit
to meeseeksmachine/zarr-python
that referenced
this pull request
Jul 31, 2025
dstansby
added a commit
that referenced
this pull request
Jul 31, 2025
…3314) Co-authored-by: David Stansby <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
For 3.1.1 I did the release on a release brach, and then set up milestones so we can milestone PRs for 3.1.2 and get automatic backports, but still develop major/API breaking code on the
mainbranch. This seems to work quite well, so this PR has some updates for that workflow:main