chore: resolve open dependabot security alerts by jonathannorris · Pull Request #392 · open-feature/python-sdk-contrib · GitHub
Skip to content

chore: resolve open dependabot security alerts - #392

Merged
gruebel merged 1 commit into
mainfrom
chore/dependabot-alerts
May 19, 2026
Merged

chore: resolve open dependabot security alerts#392
gruebel merged 1 commit into
mainfrom
chore/dependabot-alerts

Conversation

@jonathannorris

@jonathannorris jonathannorris commented May 19, 2026

Copy link
Copy Markdown
Member

Summary

  • Bumped urllib3 2.6.3 -> 2.7.0 via uv lock --upgrade-package urllib3 to resolve two high-severity transitive vulnerabilities

Dependabot Alerts Resolved

Alert Package Severity Fix
#32 urllib3 high Sensitive headers forwarded across origins in proxied low-level redirects; bumped to 2.7.0 in uv.lock
#31 urllib3 high Decompression-bomb safeguards bypassed in parts of the streaming API; bumped to 2.7.0 in uv.lock

urllib3 is a transitive dependency (pulled in by botocore, docker, launchdarkly_eventsource, requests, responses). The upgrade is a single-package bump in uv.lock with no manifest changes required.

@jonathannorris
chore: resolve open dependabot security alerts
0faa700 
Signed-off-by: Jonathan Norris <jonathan.norris@dynatrace.com>
@jonathannorris
jonathannorris requested review from a team as code owners May 19, 2026 15:11
@jonathannorris
jonathannorris marked this pull request as draft May 19, 2026 15:11
gemini-code-assist[bot]
gemini-code-assist Bot reviewed May 19, 2026
View reviewed changes

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Code Review

This pull request updates the urllib3 dependency from version 2.6.3 to 2.7.0 in the uv.lock file. I have no feedback to provide.

@jonathannorris
jonathannorris marked this pull request as ready for review May 19, 2026 16:28
@codecov

codecov Bot commented May 19, 2026 •
edited
Loading

Copy link
Copy Markdown

@jonathannorris
jonathannorris requested review from a team and beeme1mr May 19, 2026 16:28
@gruebel
gruebel merged commit daafd73 into main May 19, 2026
59 checks passed
@gruebel
gruebel deleted the chore/dependabot-alerts branch May 19, 2026 17:07
aepfli added a commit that referenced this pull request Sep 14, 2026
@aepfli
test(tck): stop naming one testbed release as the flag set's boundary
78a5665 
Several comments said flagd-testbed "v3.8.0" seeds neither large-integer-flag
nor integral-float-flag. The Compose file moved to v3.10.1 and those flags are
absent from that release too, so naming one version invited the reader to
conclude the other serves them and that the failures were a pin away from going
green. They are not: open-feature/flagd-testbed#392 is what adds the flags, and
it is open.

Now phrased as no released testbed seeding them, which stays true until #392
lands and false the moment it does -- which is when these comments should be
revisited anyway.

Signed-off-by: Simon Schrottner <simon.schrottner@flagsmith.com>
aepfli added a commit that referenced this pull request Sep 14, 2026
@aepfli
test(tck): stop naming one testbed release as the flag set's boundary
29f423e 
Several comments said flagd-testbed "v3.8.0" seeds neither large-integer-flag
nor integral-float-flag. The Compose file moved to v3.10.1 and those flags are
absent from that release too, so naming one version invited the reader to
conclude the other serves them and that the failures were a pin away from going
green. They are not: open-feature/flagd-testbed#392 is what adds the flags, and
it is open.

Now phrased as no released testbed seeding them, which stays true until #392
lands and false the moment it does -- which is when these comments should be
revisited anyway.

Signed-off-by: Simon Schrottner <simon.schrottner@flagsmith.com>
aepfli added a commit that referenced this pull request Sep 15, 2026
@aepfli
test(tck): stop naming one testbed release as the flag set's boundary
a7cfe8f 
Several comments said flagd-testbed "v3.8.0" seeds neither large-integer-flag
nor integral-float-flag. The Compose file moved to v3.10.1 and those flags are
absent from that release too, so naming one version invited the reader to
conclude the other serves them and that the failures were a pin away from going
green. They are not: open-feature/flagd-testbed#392 is what adds the flags, and
it is open.

Now phrased as no released testbed seeding them, which stays true until #392
lands and false the moment it does -- which is when these comments should be
revisited anyway.

Signed-off-by: Simon Schrottner <simon.schrottner@flagsmith.com>
aepfli added a commit that referenced this pull request Sep 15, 2026
@aepfli
test(tck): stop naming one testbed release as the flag set's boundary
cb9bc5b 
Several comments said flagd-testbed "v3.8.0" seeds neither large-integer-flag
nor integral-float-flag. The Compose file moved to v3.10.1 and those flags are
absent from that release too, so naming one version invited the reader to
conclude the other serves them and that the failures were a pin away from going
green. They are not: open-feature/flagd-testbed#392 is what adds the flags, and
it is open.

Now phrased as no released testbed seeding them, which stays true until #392
lands and false the moment it does -- which is when these comments should be
revisited anyway.

Signed-off-by: Simon Schrottner <simon.schrottner@flagsmith.com>
aepfli added a commit that referenced this pull request Sep 16, 2026
@aepfli
test(tck): stop naming one testbed release as the flag set's boundary
7b8775e 
Several comments said flagd-testbed "v3.8.0" seeds neither large-integer-flag
nor integral-float-flag. The Compose file moved to v3.10.1 and those flags are
absent from that release too, so naming one version invited the reader to
conclude the other serves them and that the failures were a pin away from going
green. They are not: open-feature/flagd-testbed#392 is what adds the flags, and
it is open.

Now phrased as no released testbed seeding them, which stays true until #392
lands and false the moment it does -- which is when these comments should be
revisited anyway.

Signed-off-by: Simon Schrottner <simon.schrottner@flagsmith.com>
aepfli added a commit that referenced this pull request Sep 16, 2026
@aepfli
test(tck): stop naming one testbed release as the flag set's boundary
73af0de 
Several comments said flagd-testbed "v3.8.0" seeds neither large-integer-flag
nor integral-float-flag. The Compose file moved to v3.10.1 and those flags are
absent from that release too, so naming one version invited the reader to
conclude the other serves them and that the failures were a pin away from going
green. They are not: open-feature/flagd-testbed#392 is what adds the flags, and
it is open.

Now phrased as no released testbed seeding them, which stays true until #392
lands and false the moment it does -- which is when these comments should be
revisited anyway.

Signed-off-by: Simon Schrottner <simon.schrottner@flagsmith.com>
aepfli added a commit that referenced this pull request Sep 16, 2026
@aepfli
test(tck): stop naming one testbed release as the flag set's boundary
e412321 
Several comments said flagd-testbed "v3.8.0" seeds neither large-integer-flag
nor integral-float-flag. The Compose file moved to v3.10.1 and those flags are
absent from that release too, so naming one version invited the reader to
conclude the other serves them and that the failures were a pin away from going
green. They are not: open-feature/flagd-testbed#392 is what adds the flags, and
it is open.

Now phrased as no released testbed seeding them, which stays true until #392
lands and false the moment it does -- which is when these comments should be
revisited anyway.

Signed-off-by: Simon Schrottner <simon.schrottner@flagsmith.com>
aepfli added a commit that referenced this pull request Sep 16, 2026
@aepfli
test(tck): stop naming one testbed release as the flag set's boundary
feae3bc 
Several comments said flagd-testbed "v3.8.0" seeds neither large-integer-flag
nor integral-float-flag. The Compose file moved to v3.10.1 and those flags are
absent from that release too, so naming one version invited the reader to
conclude the other serves them and that the failures were a pin away from going
green. They are not: open-feature/flagd-testbed#392 is what adds the flags, and
it is open.

Now phrased as no released testbed seeding them, which stays true until #392
lands and false the moment it does -- which is when these comments should be
revisited anyway.

Signed-off-by: Simon Schrottner <simon.schrottner@flagsmith.com>
aepfli added a commit that referenced this pull request Sep 16, 2026
@aepfli
test(tck): stop naming one testbed release as the flag set's boundary
c177ced 
Several comments said flagd-testbed "v3.8.0" seeds neither large-integer-flag
nor integral-float-flag. The Compose file moved to v3.10.1 and those flags are
absent from that release too, so naming one version invited the reader to
conclude the other serves them and that the failures were a pin away from going
green. They are not: open-feature/flagd-testbed#392 is what adds the flags, and
it is open.

Now phrased as no released testbed seeding them, which stays true until #392
lands and false the moment it does -- which is when these comments should be
revisited anyway.

Signed-off-by: Simon Schrottner <simon.schrottner@flagsmith.com>
aepfli added a commit that referenced this pull request Oct 1, 2026
@aepfli
test(tck): stop naming one testbed release as the flag set's boundary
ca656ba 
Several comments said flagd-testbed "v3.8.0" seeds neither large-integer-flag
nor integral-float-flag. The Compose file moved to v3.10.1 and those flags are
absent from that release too, so naming one version invited the reader to
conclude the other serves them and that the failures were a pin away from going
green. They are not: open-feature/flagd-testbed#392 is what adds the flags, and
it is open.

Now phrased as no released testbed seeding them, which stays true until #392
lands and false the moment it does -- which is when these comments should be
revisited anyway.

Signed-off-by: Simon Schrottner <simon.schrottner@flagsmith.com>
aepfli added a commit that referenced this pull request Oct 1, 2026
@aepfli
test(tck): stop naming one testbed release as the flag set's boundary
ef108f2 
Several comments said flagd-testbed "v3.8.0" seeds neither large-integer-flag
nor integral-float-flag. The Compose file moved to v3.10.1 and those flags are
absent from that release too, so naming one version invited the reader to
conclude the other serves them and that the failures were a pin away from going
green. They are not: open-feature/flagd-testbed#392 is what adds the flags, and
it is open.

Now phrased as no released testbed seeding them, which stays true until #392
lands and false the moment it does -- which is when these comments should be
revisited anyway.

Signed-off-by: Simon Schrottner <simon.schrottner@flagsmith.com>
aepfli added a commit that referenced this pull request Oct 2, 2026
@aepfli
test(tck): stop naming one testbed release as the flag set's boundary
df07008 
Several comments said flagd-testbed "v3.8.0" seeds neither large-integer-flag
nor integral-float-flag. The Compose file moved to v3.10.1 and those flags are
absent from that release too, so naming one version invited the reader to
conclude the other serves them and that the failures were a pin away from going
green. They are not: open-feature/flagd-testbed#392 is what adds the flags, and
it is open.

Now phrased as no released testbed seeding them, which stays true until #392
lands and false the moment it does -- which is when these comments should be
revisited anyway.

Signed-off-by: Simon Schrottner <simon.schrottner@flagsmith.com>
aepfli added a commit that referenced this pull request Oct 2, 2026
@aepfli
test(tck): stop naming one testbed release as the flag set's boundary
cb43407 
Several comments said flagd-testbed "v3.8.0" seeds neither large-integer-flag
nor integral-float-flag. The Compose file moved to v3.10.1 and those flags are
absent from that release too, so naming one version invited the reader to
conclude the other serves them and that the failures were a pin away from going
green. They are not: open-feature/flagd-testbed#392 is what adds the flags, and
it is open.

Now phrased as no released testbed seeding them, which stays true until #392
lands and false the moment it does -- which is when these comments should be
revisited anyway.

Signed-off-by: Simon Schrottner <simon.schrottner@flagsmith.com>
aepfli added a commit that referenced this pull request Oct 5, 2026
@aepfli
test(tck): stop naming one testbed release as the flag set's boundary
1076c77 
Several comments said flagd-testbed "v3.8.0" seeds neither large-integer-flag
nor integral-float-flag. The Compose file moved to v3.10.1 and those flags are
absent from that release too, so naming one version invited the reader to
conclude the other serves them and that the failures were a pin away from going
green. They are not: open-feature/flagd-testbed#392 is what adds the flags, and
it is open.

Now phrased as no released testbed seeding them, which stays true until #392
lands and false the moment it does -- which is when these comments should be
revisited anyway.

Signed-off-by: Simon Schrottner <simon.schrottner@flagsmith.com>
aepfli added a commit that referenced this pull request Oct 8, 2026
@aepfli
test(tck): stop naming one testbed release as the flag set's boundary
aa6d166 
Several comments said flagd-testbed "v3.8.0" seeds neither large-integer-flag
nor integral-float-flag. The Compose file moved to v3.10.1 and those flags are
absent from that release too, so naming one version invited the reader to
conclude the other serves them and that the failures were a pin away from going
green. They are not: open-feature/flagd-testbed#392 is what adds the flags, and
it is open.

Now phrased as no released testbed seeding them, which stays true until #392
lands and false the moment it does -- which is when these comments should be
revisited anyway.

Signed-off-by: Simon Schrottner <simon.schrottner@flagsmith.com>
aepfli added a commit that referenced this pull request Oct 8, 2026
@aepfli
test(tck): stop naming one testbed release as the flag set's boundary
a8edd6b 
Several comments said flagd-testbed "v3.8.0" seeds neither large-integer-flag
nor integral-float-flag. The Compose file moved to v3.10.1 and those flags are
absent from that release too, so naming one version invited the reader to
conclude the other serves them and that the failures were a pin away from going
green. They are not: open-feature/flagd-testbed#392 is what adds the flags, and
it is open.

Now phrased as no released testbed seeding them, which stays true until #392
lands and false the moment it does -- which is when these comments should be
revisited anyway.

Signed-off-by: Simon Schrottner <simon.schrottner@flagsmith.com>
aepfli added a commit that referenced this pull request Oct 9, 2026
@aepfli
test(tck): stop naming one testbed release as the flag set's boundary
fb884e2 
Several comments said flagd-testbed "v3.8.0" seeds neither large-integer-flag
nor integral-float-flag. The Compose file moved to v3.10.1 and those flags are
absent from that release too, so naming one version invited the reader to
conclude the other serves them and that the failures were a pin away from going
green. They are not: open-feature/flagd-testbed#392 is what adds the flags, and
it is open.

Now phrased as no released testbed seeding them, which stays true until #392
lands and false the moment it does -- which is when these comments should be
revisited anyway.

Signed-off-by: Simon Schrottner <simon.schrottner@flagsmith.com>
aepfli added a commit that referenced this pull request Oct 9, 2026
@aepfli
test(tck): stop naming one testbed release as the flag set's boundary
2c3ec87 
Several comments said flagd-testbed "v3.8.0" seeds neither large-integer-flag
nor integral-float-flag. The Compose file moved to v3.10.1 and those flags are
absent from that release too, so naming one version invited the reader to
conclude the other serves them and that the failures were a pin away from going
green. They are not: open-feature/flagd-testbed#392 is what adds the flags, and
it is open.

Now phrased as no released testbed seeding them, which stays true until #392
lands and false the moment it does -- which is when these comments should be
revisited anyway.

Signed-off-by: Simon Schrottner <simon.schrottner@flagsmith.com>
aepfli added a commit that referenced this pull request Oct 14, 2026
@aepfli
test(tck): stop naming one testbed release as the flag set's boundary
fbca402 
Several comments said flagd-testbed "v3.8.0" seeds neither large-integer-flag
nor integral-float-flag. The Compose file moved to v3.10.1 and those flags are
absent from that release too, so naming one version invited the reader to
conclude the other serves them and that the failures were a pin away from going
green. They are not: open-feature/flagd-testbed#392 is what adds the flags, and
it is open.

Now phrased as no released testbed seeding them, which stays true until #392
lands and false the moment it does -- which is when these comments should be
revisited anyway.

Signed-off-by: Simon Schrottner <simon.schrottner@flagsmith.com>
aepfli added a commit that referenced this pull request Oct 14, 2026
@aepfli
test(tck): stop naming one testbed release as the flag set's boundary
4d8fab1 
Several comments said flagd-testbed "v3.8.0" seeds neither large-integer-flag
nor integral-float-flag. The Compose file moved to v3.10.1 and those flags are
absent from that release too, so naming one version invited the reader to
conclude the other serves them and that the failures were a pin away from going
green. They are not: open-feature/flagd-testbed#392 is what adds the flags, and
it is open.

Now phrased as no released testbed seeding them, which stays true until #392
lands and false the moment it does -- which is when these comments should be
revisited anyway.

Signed-off-by: Simon Schrottner <simon.schrottner@flagsmith.com>
aepfli added a commit that referenced this pull request Oct 14, 2026
@aepfli
test(tck): stop naming one testbed release as the flag set's boundary
00535a5 
Several comments said flagd-testbed "v3.8.0" seeds neither large-integer-flag
nor integral-float-flag. The Compose file moved to v3.10.1 and those flags are
absent from that release too, so naming one version invited the reader to
conclude the other serves them and that the failures were a pin away from going
green. They are not: open-feature/flagd-testbed#392 is what adds the flags, and
it is open.

Now phrased as no released testbed seeding them, which stays true until #392
lands and false the moment it does -- which is when these comments should be
revisited anyway.

Signed-off-by: Simon Schrottner <simon.schrottner@flagsmith.com>
aepfli added a commit that referenced this pull request Oct 14, 2026
@aepfli
test(tck): stop naming one testbed release as the flag set's boundary
4351b18 
Several comments said flagd-testbed "v3.8.0" seeds neither large-integer-flag
nor integral-float-flag. The Compose file moved to v3.10.1 and those flags are
absent from that release too, so naming one version invited the reader to
conclude the other serves them and that the failures were a pin away from going
green. They are not: open-feature/flagd-testbed#392 is what adds the flags, and
it is open.

Now phrased as no released testbed seeding them, which stays true until #392
lands and false the moment it does -- which is when these comments should be
revisited anyway.

Signed-off-by: Simon Schrottner <simon.schrottner@flagsmith.com>
aepfli added a commit that referenced this pull request Oct 16, 2026
@aepfli
test(tck): stop naming one testbed release as the flag set's boundary
8da0a74 
Several comments said flagd-testbed "v3.8.0" seeds neither large-integer-flag
nor integral-float-flag. The Compose file moved to v3.10.1 and those flags are
absent from that release too, so naming one version invited the reader to
conclude the other serves them and that the failures were a pin away from going
green. They are not: open-feature/flagd-testbed#392 is what adds the flags, and
it is open.

Now phrased as no released testbed seeding them, which stays true until #392
lands and false the moment it does -- which is when these comments should be
revisited anyway.

Signed-off-by: Simon Schrottner <simon.schrottner@flagsmith.com>
aepfli added a commit that referenced this pull request Oct 16, 2026
@aepfli
test(tck): stop naming one testbed release as the flag set's boundary
4df7e58 
Several comments said flagd-testbed "v3.8.0" seeds neither large-integer-flag
nor integral-float-flag. The Compose file moved to v3.10.1 and those flags are
absent from that release too, so naming one version invited the reader to
conclude the other serves them and that the failures were a pin away from going
green. They are not: open-feature/flagd-testbed#392 is what adds the flags, and
it is open.

Now phrased as no released testbed seeding them, which stays true until #392
lands and false the moment it does -- which is when these comments should be
revisited anyway.

Signed-off-by: Simon Schrottner <simon.schrottner@flagsmith.com>
aepfli added a commit that referenced this pull request Oct 16, 2026
@aepfli
test(tck): stop naming one testbed release as the flag set's boundary
8e3330e 
Several comments said flagd-testbed "v3.8.0" seeds neither large-integer-flag
nor integral-float-flag. The Compose file moved to v3.10.1 and those flags are
absent from that release too, so naming one version invited the reader to
conclude the other serves them and that the failures were a pin away from going
green. They are not: open-feature/flagd-testbed#392 is what adds the flags, and
it is open.

Now phrased as no released testbed seeding them, which stays true until #392
lands and false the moment it does -- which is when these comments should be
revisited anyway.

Signed-off-by: Simon Schrottner <simon.schrottner@flagsmith.com>
aepfli added a commit that referenced this pull request Oct 16, 2026
@aepfli
test(tck): stop naming one testbed release as the flag set's boundary
7191789 
Several comments said flagd-testbed "v3.8.0" seeds neither large-integer-flag
nor integral-float-flag. The Compose file moved to v3.10.1 and those flags are
absent from that release too, so naming one version invited the reader to
conclude the other serves them and that the failures were a pin away from going
green. They are not: open-feature/flagd-testbed#392 is what adds the flags, and
it is open.

Now phrased as no released testbed seeding them, which stays true until #392
lands and false the moment it does -- which is when these comments should be
revisited anyway.

Signed-off-by: Simon Schrottner <simon.schrottner@flagsmith.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@matthewelwell matthewelwell matthewelwell approved these changes
@gruebel gruebel gruebel approved these changes
@beeme1mr beeme1mr Awaiting requested review from beeme1mr
+1 more reviewer
@gemini-code-assist gemini-code-assist[bot] gemini-code-assist[bot] left review comments
Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@jonathannorris @matthewelwell @gruebel