Skip to content

Conversation

@tkelman
Copy link
Contributor

@tkelman tkelman commented Oct 26, 2025

This is a combination of #9811 #10033 and the test data format updates from #8072. Updating ruamel-yaml is necessary for Python 3.14 support #9783 #9914. I may be missing regeneration of a few more lockfiles, not sure what the procedure is for updating all of those. I updated them by hand, hopefully same result as running the regenerate lockfiles script

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@tkelman tkelman mentioned this pull request Jan 9, 2026
2 tasks
dependabot bot and others added 4 commits January 29, 2026 06:23
Bumps ruamel-yaml from 0.17.21 to 0.19.1.

---
updated-dependencies:
- dependency-name: ruamel-yaml
  dependency-version: 0.19.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
* ruamel-yaml 0.17.22 comes with a style change that affects test results.
  From https://sourceforge.net/p/ruamel-yaml/code/ci/0.17.22/tree/CHANGES

> plain scalars: put single words longer than width on a line of their own, instead of after the previous line

* ruamel-yaml 0.17.29 introduces an issue with add_constructor and
  DEFAULT_MAPPING_TAG, and the issue is fixed with 0.17.36 [1], hence the
  new lower bound.

[1] https://sourceforge.net/p/ruamel-yaml/tickets/482/

(cherry picked from commit 1b5ef38)
@tkelman tkelman force-pushed the v2-update-ruamel-yaml branch from 4b88a85 to d3a78fc Compare February 1, 2026 16:55
@tkelman tkelman changed the title [v2] Bump ruamel-yaml from 0.17.21 to 0.18.16 [v2] Bump ruamel-yaml from 0.17.21 to 0.19.1 Feb 1, 2026
@reneleonhardt
Copy link

Thank you for your work!

Is there a reason why there's no review and merge to update an 4 years old dependency to support Python 3.14 before 3.15 will be released? 🤔

@tkelman
Copy link
Contributor Author

tkelman commented Feb 2, 2026

I don't know why keeping dependency versioning updated in a reasonable manner is such a low maintenance priority here that it has taken months to years to get this kind of contribution reviewed. It's frustrating as a downstream packager.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants