.github/workflows/release.yml: Fix release #296
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
When ansible-community#294, I didn't notice that the python version was not inside quotes, leading to python version being parsed as 3.1 and not 3.10. Breaking the release workflow. Add missing quotes. Signed-off-by: Arnaud Patard <arnaud.patard@collabora.com>
oraNod
approved these changes
Jan 23, 2025
|
@oraNod I guess I've to create a minor release to run again the release workflow and publish the release to pypi ? |
|
@apatard Hey, I think it might be better to delete the failed release and try again. The steps in this post seem good: https://vishnugopal.com/2020/05/02/recreating-a-failed-github-release-with-the-same-tag/ Hope that helps and give me a shout if you need anything. Cheers. |
|
@oraNod It seems to have worked. Thanks a lot ! |
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 #294, I didn't notice that the python version was not inside quotes, leading to python version being parsed as 3.1 and not 3.10. Breaking the release workflow.
Add missing quotes.