chore: bump version.py to 2.3.0.dev + refresh RELEASE_MEMO#1470
Closed
dimitri-yatsenko wants to merge 1 commit into
Closed
chore: bump version.py to 2.3.0.dev + refresh RELEASE_MEMO#1470dimitri-yatsenko wants to merge 1 commit into
dimitri-yatsenko wants to merge 1 commit into
Conversation
- src/datajoint/version.py: 2.2.4 → 2.3.0.dev. The GitHub Actions release flow auto-overwrites this at tag time; the dev marker reflects the current development target between releases. - RELEASE_MEMO.md: refresh the branch table from "2.1.x" (stale; predated the 2.1 and 2.2 release lines) to "2.3.x". Part of T18 (cross-cutting release plumbing).
Member
Author
|
Closing — |
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
Part of T18 (cross-cutting 2.3 release plumbing).
The GitHub Actions release flow auto-overwrites `version.py` at tag time, but the dev marker matters mid-cycle: it tells anyone reading the file (including downstream tools that parse `version`) what the next release target is.
Test plan