Repository navigation
Add GitHub Release workflow on root version bump - #1
Closed
Emrys-Merlin wants to merge 1 commit into
Closed
Emrys-Merlin wants to merge 1 commit into
Emrys-Merlin wants to merge 1 commit into
Conversation
Create v{version} from pyproject.toml when that tag is missing on main.
Co-authored-by: Cursor <cursoragent@cursor.com>
Author
|
Superseded by #2 |
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.
This PR introduces a very minimal CI workflow to publish a new GitHub release on a version change inside root's pyproject.toml.
Having a GitHub release drastically simplifies publishing the package on conda-forge, which is a process I would like to get started (for better integration into the OpenFold-3 pixi environments).
If you have other plans for how you want to handle versioning and releasing in the future, please feel free to close or adapt the PR. I'm by no means attached to this approach. I aimed for minimal changes to the current repo setup while still creating the release page I need.
Thanks for this library! This is very cool :)