Limits poetry so it doesn't upgrade to v2 #819
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
…seems to have some breaking configuration changes currently. I'll cherry pick this commit into it's own pull request if this works.
|
It seems like Adam would like to go ahead with the changes in a bunch of tickets for text changes and accessibility changes rather than waiting for Jing to return in March. There are revisions to the info-pages repo and also revisions to the main application. All these changes are combined and deployed to dev with the |
datadavev
approved these changes
Feb 19, 2025
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.
The github actions script was updating to v2 which was released on Jan 5th, 2025. This caused some configuration warnings and an outright failure with the action because of some breaking config incompatibilities. See #818 . It was decided to stay with the 1.x version rather than updating everything to 2.x before doing more analysis to be sure it is a non-breaking and useful upgrade.
The download/install/update script for the github action is able to take a version number which I'm setting to 1.8.5 (latest of 1.x series at this point).
Locking ansible to this version, also.
In the pyproject.toml, limiting it so it will not update to version 2.