group python updates

[JPrevost]

Purpose and background context

Describe the overall purpose of the PR changes and any useful background context.

How can a reviewer manually see the effects of these changes?

Explain how to see the proposed changes in the application if possible.

Delete this section if it isn't applicable to the PR.

Includes new or updated dependencies?

YES | NO

Changes expectations for external applications?

YES | NO

What are the relevant tickets?

• Include links to Jira Software and/or Jira Service Management tickets here.

Code review

• Code review best practices are documented here and you are encouraged to have a constructive dialogue with your reviewers about their preferences and expectations.

[renovate]

Reconfigure PR Results

This is a reconfigure PR comment to help you understand and re-configure your renovate bot settings. If this Reconfigure PR were to be merged, we'd expect to see the following outcome:

---

Detected Package Files

• Dockerfile (dockerfile)
• .github/workflows/ci.yml (github-actions)
• .github/workflows/dev-build.yml (github-actions)
• .github/workflows/prod-deploy.yml (github-actions)
• .github/workflows/stage-build.yml (github-actions)
• pyproject.toml (pep621)
• .python-version (pyenv)
• renovate.json (renovate-config)

Configuration Summary

Based on the default config's presets, Renovate will:

• Hopefully safe environment variables to allow users to configure.
• Show all Merge Confidence badges for pull requests.
• Enable Renovate Dependency Dashboard creation.
• Use semantic commit type fix for dependencies and chore for all others if semantic commits are in use.
• Ignore node_modules, bower_components, vendor and various test/tests (except for nuget) directories.
• Group known monorepo packages together.
• Use curated list of recommended non-monorepo package groupings.
• Show only the Age and Confidence Merge Confidence badges for pull requests.
• Apply crowd-sourced package replacement rules.
• Apply crowd-sourced workarounds for known problems with packages.
• Ensure that every dependency pinned by digest and sourced from Forgejo contains a link to the commit-to-commit diff
• Ensure that every dependency pinned by digest and sourced from Gitea contains a link to the commit-to-commit diff
• Ensure that every dependency pinned by digest and sourced from GitHub.com and Github enterprise contains a link to the commit-to-commit diff
• Ensure that every dependency pinned by digest and sourced from GitLab.com contains a link to the commit-to-commit diff
• Correctly link to the source code for golang.org/x packages
• Link to pkg.go.dev/... for golang.org/x packages' title
• Provide a link to octochangelog's improved breakdown for Renovate's changelogs
• Pin Docker digests.
• Pin github-action digests.
• Enable Renovate configuration migration PRs when needed.
• Pin dependency versions for development dependencies.
• Recommended configuration for abandoned packages, treating packages without a release for 1 year as abandoned, while taking into account community-sourced overrides.
• Wait until the npm package is three days old before raising the update. This a) introduces a short delay to allow for malware researchers and scanners to (possibly) detect any malicious behaviour in packages, and b) prevents the maintainer and/or NPM from unpublishing a package you already upgraded to, breaking builds.
• Run lock file maintenance (updates) early Monday mornings.
• Schedule during typical non-office hours on weekdays (i.e., 10 PM - 5 AM) and anytime on weekends.
• Run Renovate on following schedule: * 0-4,22-23 * * 1-5,* * * * 0,6

---

What to Expect

With your current configuration, Renovate will create 4 Pull Requests:

Pin dependencies

• Schedule: ["* 0-4,22-23 * * 1-5","* * * * 0,6"]
• Branch name: renovate/pin-dependencies
• Merge into: main
• Upgrade aws-actions/configure-aws-credentials to 517a711dbcd0e402f90c77e7e2f81e849156e31d
• Upgrade ghcr.io/astral-sh/uv to sha256:edd1fd89f3e5b005814cc8f777610445d7b7e3ed05361f9ddfae67bebfe8456a
• Upgrade mitlibraries/.github to ed81322385810830d3b88f73557e6e1f35ce062a
• Upgrade public.ecr.aws/lambda/python to sha256:7617cf2cb4f420064b361b9abef0cabfe025734fcde775967ed91e27e95bbb0d

Update ghcr.io/astral-sh/uv Docker tag to v0.11.31

• Schedule: ["* 0-4,22-23 * * 1-5","* * * * 0,6"]
• Branch name: renovate/dockerfile-minor-patch
• Merge into: main
• Upgrade ghcr.io/astral-sh/uv to sha256:ecd4de2f060c64bea0ff8ecb182ddf46ba3fcccdc8a60cfdbaf20d1a047d7437

Update public.ecr.aws/lambda/python Docker tag to v3.15

• Schedule: ["* 0-4,22-23 * * 1-5","* * * * 0,6"]
• Branch name: renovate/public.ecr.aws-lambda-python-3.x
• Merge into: main
• Upgrade public.ecr.aws/lambda/python to sha256:adcb1e39830bd24c19d1ddff38928c02839a551e987d155a2e4da43f21360163

Lock file maintenance

• Schedule: ["* 0-3 * * 1"]
• Branch name: renovate/lock-file-maintenance
• Merge into: main
• Regenerate lock files to use latest dependency versions

🚸 PR creation will be limited to maximum 2 per hour, so it doesn't swamp any CI resources or overwhelm the project. See docs for prHourlyLimit for details.