Skip to content

[v2] Bump ruamel-yaml from 0.17.21 to 0.19.1#9814

Closed
tkelman wants to merge 4 commits intoaws:v2from
tkelman:v2-update-ruamel-yaml
Closed

[v2] Bump ruamel-yaml from 0.17.21 to 0.19.1#9814
tkelman wants to merge 4 commits intoaws:v2from
tkelman:v2-update-ruamel-yaml

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.

@tkelman
Copy link
Contributor Author

tkelman commented Feb 26, 2026

9458b2f is also a valid fix for the test format change. that can either be added into #10033 or it might be merged in #10102 (along with quite a few other changes unrelated to ruamel-yaml)

@tkelman tkelman closed this Feb 26, 2026
@tkelman tkelman deleted the v2-update-ruamel-yaml branch February 26, 2026 18:29
@reneleonhardt
Copy link

reneleonhardt commented Feb 27, 2026

If it's any consolation, you're not alone, many maintainers don't allow manual dependency updates or enabling automatic dependabot / renovatebot pull requests to avoid this tedious work.

Sometimes it helps to start an issue / discussion / comment before going through all the trouble of doing the actual work for them and waiting for reviews eternally.

Keep in mind that not all Open-Source projects are community-driven, or at least embracing and encouraging the manual work of voluntary contributors, or accepting the help of Claude Code.

Regarding technical debt, most projects don't even audit their dependencies with free actions like https://github.com/aquasecurity/trivy-action or npm audit, let alone using cosign or Trusted Publishing, so there's not much you can do as a contributor anyway to improve compatibility and supply chain security for them...

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