chore: bump version to v2.5.0 - #153
Merged
Merged
Conversation
Tag v2.4.2 already existed (manual tag by Filippi for the JOSS/MesoNH sync), ahead of Version.h's v2.3.0. Bumping to v2.5.0 to mark the pip-installable wheels release and keep Version.h, the git tag, and the PyPI version in sync going forward. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
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.
Bumps
Version.hfromv2.3.0tov2.5.0.Tag
v2.4.2already exists (manual tag by @filippi_j for the JOSS/MesoNH sync), sov2.3.0was behind an already-published release. Going tov2.5.0keeps the version increasing and marks the long-awaitedpip install forefirerelease (#151).Not merging automatically — will merge manually after tagging/release plan is confirmed.