Automatic versioning and new v1.3.2 ready for release #313
Merged
Conversation
…cated by libsbml), and add automatic versioning to pyproject and to __init__
…launch new releases
Collaborator
Author
|
If the changes look good, we can merge and then release v1.3.2 |
murrayrm
approved these changes
Sep 15, 2025
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
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.
After recent merges from PRs #311 and #312 a new release was not set. This PR updates the package version so it can be released. In that process, I automated the versioning for the package and added instructions in
docs/develop.rstfor all future releases.This PR will also enable users to run
biocrnpyler.__version__to check which version they are running.Additional fixes/changes:
pip install .)