Skip to content
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.

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

Bump Python from 3.12.6 to 3.12.8 #19454

Merged
merged 5 commits into from
Jan 23, 2025

Conversation

nubtron
Copy link
Contributor

@nubtron nubtron commented Jan 22, 2025

What does this PR do?

Bump the Python version from 3.12.6 to 3.12.8 to address a CVE.

Review checklist (to be filled by reviewers)

  • Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
  • Add the qa/skip-qa label if the PR doesn't need to be tested during QA.
  • If you need to backport this PR to another branch, you can add the backport/<branch-name> label to the PR and it will automatically open a backport PR once this one is merged

@nubtron nubtron force-pushed the nubtron/bump_python_from_3.12.6_to_3.12.8 branch from 283b074 to 0e09cfa Compare January 22, 2025 13:08
@nubtron nubtron marked this pull request as ready for review January 22, 2025 14:55
@nubtron nubtron requested review from a team as code owners January 22, 2025 14:55
@nubtron nubtron added this pull request to the merge queue Jan 23, 2025
Copy link

codecov bot commented Jan 23, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 89.11%. Comparing base (58e21f7) to head (ab0223d).
Report is 8 commits behind head on master.

Additional details and impacted files
Flag Coverage Δ
activemq ?
cassandra ?
hive ?
hivemq ?
hudi ?
ignite ?
jboss_wildfly ?
kafka ?
presto ?
solr ?

Flags with carried forward coverage won't be shown. Click here to find out more.

Merged via the queue into master with commit d44aa43 Jan 23, 2025
41 checks passed
@nubtron nubtron deleted the nubtron/bump_python_from_3.12.6_to_3.12.8 branch January 23, 2025 09:23
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