ci: Publish to PyPI from tags #231
Merged
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
ThiefMaster
force-pushed
the
ci-pypi
branch
3 times, most recently
from
2aa87b1 to
a08820d
Compare
ThiefMaster
force-pushed
the
ci-pypi
branch
5 times, most recently
from
1b0bc0b to
98ab189
Compare
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 is for "general" releases that bump the versions of all plugins.
For the first release where everything goes to v3.3 this will publish everything, for future releases (v3.3.x) which will only update some plugins, any wheel that already exists on PyPI with the same version should simply be skipped.
Intermediate releases where just specific plugins get updated (within the allowed range of the
indico-pluginsmeta package) are not handled by this job. We'll have to add a separate one that's either triggered manually (not ideal), from pushes that bump the version of a plugin (maybe a bit too implicit?) or start creating tags for individual plugin releases (vc-zoom/v3.3.1or similar).