Fix ruamel.yaml pinning. Fixes docs and test process for EC2. #346
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
|
@ottobackwards would you be interested in reviewing these updated testing instructions? I needed to update the whole process as several steps no longer work due to various deprecations. |
|
The reported py-1.11.0 vulnerability appears to only affect Subversion, so it can be ignored. |
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.
Fixes #345
Also addresses outdated build and test process on EC2 by moving to AL2023 process.
Also addresses specific deprecations blocking testing by updating several processes like sphinx build and use of pyenv for tox processes. Other deprecation notices remain but will be addressed separately - this PR is focused on a clean build process for the current code and fixing this blocking issue.