Skip to content

Conversation

@swember
Copy link
Contributor

@swember swember commented Sep 1, 2025

Due to Future library vulnerability issue we need to stop using it.

Copy link
Contributor

@pkopac pkopac left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This might be possibly a breaking change due to the futures being part of the API of the SDK, ie. chartmogul.Ping.ping(config).get(). You'll need to have a look how the behavior changes and whether we can make it backwards compatible somehow (different library?, mock methods?) or whether we need to issue a major version.
Otherwise scripts would just get randomly broken upon upgrade 👎

Copy link
Contributor

@pkopac pkopac left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Never mind me, I thought you were removing promise 🤦

@swember swember requested review from a team, anawolak and tudorpavel and removed request for a team September 2, 2025 08:10
@swember swember merged commit 43f5eb6 into main Sep 2, 2025
6 checks passed
@swember swember deleted the dmitriydavydov/sc-71013/drop-future-lib-dependency-from-python-lib branch September 2, 2025 09:55
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