Thanks for calling this out - we actually have a script <https://github.com/apache/beam/blob/master/.github/workflows/update_python_dependencies.yml> to do this automatically after the release like you're suggesting. This release, it ran and the resulting PR is currently assigned to me. I have not merged it yet because there are (seemingly real) CI failures which I haven't had a chance to deal with yet. - https://github.com/apache/beam/pull/31885.
Thanks, Danny On Thu, Aug 8, 2024 at 9:08 PM Robert Bradshaw via dev <dev@beam.apache.org> wrote: > I noticed when updating a dependency in the base image requirements and > running > > ./gradlew :sdks:python:container:generatePythonRequirementsAll > > that a *lot* of other dependencies changed as well. Most were minor > version bumps, but this seems less than ideal. I wonder if we should > run this script periodically (maybe just after a release to let things > bake for the next one?) rather than put it on whoever is updating a > dependency to manually update everything else. >
