Repository navigation
Release container images manually from the latest version on PyPI - #322
Merged
Merged
Conversation
Signed-off-by: Sylvain Hellegouarch <sh@defuze.org>
|
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.
Summary
The 1.21.1 release published to PyPI, but the container job gave up after 5 minutes: PyPI's JSON API listed 1.21.1 while the index pip reads still stopped at 1.21.0, for well over 15 minutes.
workflow_dispatch): packages the latest chaostoolkit that pip can actually install from PyPI, or the version given in the new optionalversioninput. The image is taggedlatestand with that version, as before.workflow_callfromrelease.yaml): unchanged, it packages the release tag.Usage
Testing
actionlintclean.pip download --no-deps chaostoolkit, then reading the wheel's name) run locally gives the version pip installs.