Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Avoid ruamel.yaml 0.18.7-0.18.8 due to regression #4462

Merged
merged 1 commit into from
Jan 3, 2025
Merged

Conversation

ssbarnea
Copy link
Member

@ssbarnea ssbarnea commented Jan 3, 2025

Update dependencies and avoid use of newer ruamel.yaml versions due to formatting regression from https://sourceforge.net/p/ruamel-yaml/tickets/534/

Update dependencies and avoid use of newer ruamel.yaml versions
due to regression from https://sourceforge.net/p/ruamel-yaml/tickets/534/
@ssbarnea ssbarnea requested a review from a team as a code owner January 3, 2025 09:20
@github-actions github-actions bot added the skip-changelog Can be missed from the changelog. label Jan 3, 2025
@ssbarnea ssbarnea added bug and removed skip-changelog Can be missed from the changelog. labels Jan 3, 2025
@ssbarnea ssbarnea requested a review from abhikdps January 3, 2025 09:21
@ssbarnea ssbarnea enabled auto-merge (squash) January 3, 2025 09:30
@ssbarnea ssbarnea merged commit 37dd23d into main Jan 3, 2025
30 checks passed
@ssbarnea ssbarnea deleted the chore/deps branch January 3, 2025 09:32
@@ -10,7 +10,7 @@ jsonschema>=4.10.0 # MIT, version needed for improved errors
packaging>=21.3 # Apache-2.0,BSD-2-Clause
pathspec>=0.10.3 # Mozilla Public License 2.0 (MPL 2.0)
pyyaml>=5.4.1 # MIT (centos 9 has 5.3.1)
ruamel.yaml>=0.18.5 # MIT
ruamel.yaml>=0.18.5,!=0.18.7,!=0.18.8 # MIT
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

good fix for future proofing since 18.9 came out :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

3 participants