deps: Bump flagsmith-flag-engine to 11.0.0 - #242
Open
matthewelwell wants to merge 1 commit into
Open
Conversation
Engine 11.0.0's only breaking change is dropping Python 3.9 support; it requires >=3.10 and carries no API changes. Deliberately NOT marked as a breaking change for this SDK. This client already dropped Python 3.9 in 814e67e ("deps!: drop Python 3.9 support to allow urllib3 >=2.7.0", #227) and declares python = ">=3.10,<4", which shipped in 6.x. Engine 11 therefore imposes no constraint on consumers that this package does not already impose, so a major bump would signal a break that does not exist. Relocked with Poetry 2.x to preserve lock-version 2.1; the diff is the engine package block and the content-hash only. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
khvn26
approved these changes
Aug 28, 2026
1 task
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Changes
Bumps
flagsmith-flag-enginefrom^10.2.0to^11.0.0.Engine 11.0.0's only breaking change is dropping Python 3.9 support (it now
requires
>=3.10). It contains no API changes — the rest of the release isCI and dependency updates.
This is intentionally not released as a breaking change
Worth calling out explicitly, since engine 11.0.0 is itself a major bump.
This SDK already dropped Python 3.9 in 814e67e — "deps!: drop Python 3.9
support to allow urllib3 >=2.7.0" (#227) — which moved
pythonfrom">=3.9,<4"to">=3.10,<4". That has shipped:flagsmith 6.2.1on PyPIdeclares
Requires-Python: >=3.10,<4, and CI tests 3.10–3.13.So engine 11 imposes no constraint on consumers of this package that this
package does not already impose. Marking this breaking would cut a spurious
7.0.0 and signal a break that does not exist for anyone able to install 6.x
today.
Relocked with Poetry 2.x to preserve
lock-version = "2.1". Poetry 1.8 rewritesit down to 2.0, which would be unrelated churn — worth knowing, as CI installs
Poetry unpinned. The resulting diff is the engine package block plus the
content-hash.
Note on ordering
This PR unblocks two other repos.
edge-proxyandflagsmith(OSSapi/) bothdepend on this package and need engine 11, but the currently published
flagsmith 6.2.1pinsflagsmith-flag-engine<11.0.0— so their dependency setsare unsatisfiable until this is merged and released.
How did you test this code?
poetry run mypy --strict .— success, no issues in 28 source files.poetry run pytest— 115 passed, 6 failed.test_flagsmith__init__expected_headers_sent, and they fail identically onunmodified
mainwith engine 10.2.0 (verified). They stem from default-headerbehaviour in
requests 2.34.2/urllib3 2.7.0, not from this bump.