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

[Backport 7.58.x] Bump Hazelcast python client to support python 3.12 #18521

Merged
merged 1 commit into from
Sep 6, 2024

Conversation

datadog-agent-integrations-bot[bot]
Copy link
Contributor

Backport aea016b from #18520.


What does this PR do?

Bump hazelcast python client to support python 3.12

Motivation

Additional Notes

Review checklist (to be filled by reviewers)

  • Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
  • Changelog entries must be created for modifications to shipped code
  • 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

* bump hazelcast python client

* revert hatch.toml

* add changelog

(cherry picked from commit aea016b)
Copy link

codecov bot commented Sep 6, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 90.00%. Comparing base (21950c0) to head (2815c20).
Report is 3 commits behind head on 7.58.x.

Additional details and impacted files
Flag Coverage Δ
activemq ?
cassandra ?
hazelcast 92.30% <ø> (ø)
hive ?
hivemq ?
hudi ?
ignite ?
jboss_wildfly ?
kafka ?
presto ?
solr ?

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

@steveny91 steveny91 merged commit 4a86315 into 7.58.x Sep 6, 2024
36 of 37 checks passed
@steveny91 steveny91 deleted the backport-18520-to-7.58.x branch September 6, 2024 20:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants