[PR #2084/2e4d1296 backport][0.18] Add stricter upperbound for galaxy-importer to account for dropping of py3.8 #2096
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
![patchback[bot]](https://avatars.githubusercontent.com/in/21488?s=60&v=4){kind=small}
…f py3.8 (cherry picked from commit 2e4d129)
gerrod3
approved these changes
Jan 20, 2025
gerrod3
deleted the
patchback/backports/0.18/2e4d1296644193213b8bf36f5cce54f6cb3e2c31/pr-2084
branch
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 a backport of PR #2084 as merged into 0.20 (2e4d129).
Our older images <core3.49 use python3.8. A recent release of galaxy-importer now uses code not present in py3.8, and it seems they haven't been testing 3.8 for a while. So restrict to last known supported version: ansible/galaxy-importer@109c1ee