Add release GitHub actions #336
Draft
Conversation
This file contains 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.
closes #317
Add GitHub actions to publish on release
Do not merge - #315 is needed first. After transfer, the repo should automatically have access to the PyPI secrets needed by
release.ymlccds.__version__Users can now see the version of
ccdsafter importing (ccds.__version__). However, the project name is different than the module name. This means that inversion.py, we have to hard code the project name with:Instead of using:
Docs
This PR does not include versioning for docs (eg. with a "Build docs" job). That is tracked separately in #334