Release workflow #38
Merged
Release workflow #38
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
|
Nice ! just pinging @fteicht who is a bit the pypi master here |
- long description is needed, read from README.md - version number is taken from package __init__.py so that it stays synchronized. This code part is taken directly from pip setup.py. - add more metadata The version number is meant to be dynamically updated during release workflow.
- workflow is triggered also by pushs on tags matching 'v[0-9]+.[0-9]+.[0-9]+' regular pattern
- when pushing on a tag, the package version number is updated according to the tag name stripped from the initial v
- new "deploy" job (only triggered by a push on a tag):
- create the github release with the wheels as asset, and auto
generated release notes from merged PRs
- publish release on Test Pypi for forks
- publish release on Pypi for main repo airbus/discrete-optimization
fteicht
approved these changes
Sep 19, 2022
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.
When pushing on tags matching 'v[0-9]+.[0-9]+.[0-9]+' regular pattern, we trigger also the workflow which moreover
See the result of the workflow on my fork, with the github fake release and the correponding package on TestPyPI.
NB: the auto-generated release notes will be more meaningful on the main repo since it takes into account PR titles and there are no PR on my fork.