Skip to content

build: Restrict ruamel-yaml to v0.18.6 or older #542

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Jan 16, 2025
Merged

build: Restrict ruamel-yaml to v0.18.6 or older #542

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion pyproject.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -49,7 +49,7 @@ dependencies = [
"rich>=13.0.0", # databinder
"aiofile", # compatible versions controlled through miniopy-async
"make-it-sync", # compatible versions controlled through func_adl
"ruamel.yaml>=0.18",
"ruamel.yaml>=0.18,<0.18.7", # FIXME: ruamel-yaml v0.18.7 has a breaking API change relative to v0.18.6
Copy link
Member Author

@matthewfeickert matthewfeickert Jan 15, 2025

Choose a reason for hiding this comment

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

I'm selecting a temporary upper bound here instead of using the disallow syntax

"ruamel.yaml>=0.18,!=0.18.7,!=0.18.8,!=0.18.9,!=0.18.10

as the maintainer is on a release streak (maybe a bad sign after a year of nothing) and it is clear that there's an API breaking change that is going to have to get resolved, so a this is known to fail and it isn't going to get better with an upstream fix, we should cap for now.

"ccorp-yaml-include-relative-path>=0.0.4",
"filelock>=3.12.0",
"tenacity >= 9.0.0"
Expand Down
Loading