Update dependency launchdarkly-server-sdk to v9

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
launchdarkly-server-sdk	^8.3.0 -> ^9.12.3

---

Release Notes

launchdarkly/python-server-sdk (launchdarkly-server-sdk)

v9.12.3

Compare Source

Bug Fixes

• Fix overly generic type hint on File data source (#​365) (52a7499), closes #​364

v9.12.2

Compare Source

Bug Fixes

• Fix incorrect event count in failure message (#​359) (91f4163)

v9.12.1

Compare Source

Bug Fixes

• Add validation format check for SDK key (#​351)

v9.12.0

Compare Source

⚠ BREAKING CHANGES

• Drop support for Python 3.8 (eol 2024-10-07) (#​339)

Features

• Add support for plugins. (#​337) (241f6f4)
• Drop support for Python 3.8 (eol 2024-10-07) (#​339) (0207665)

v9.11.1

Compare Source

Bug Fixes

• Raise minimum eventsource dep to v1.2.4 (#​333) (5270962)

v9.11.0

Compare Source

Features

• Add postfork method to re-initialize after forking (#​329) (581fcfb)

v9.10.0

Compare Source

Features

• Inline context for custom and migration op events (#​327) (ecfd56c)

v9.9.0

Compare Source

Features

• Add support for payload filtering (#​323) (1115afb)

v9.8.1

Compare Source

Bug Fixes

• Close SSE thread on shutdown (#​320) (2210658)

v9.8.0

Compare Source

Features

• Add support for client-side prerequisite events (#​314) (3025af4)

v9.7.2

Compare Source

Bug Fixes

• Set explicit names for each spawned thread (#​311) (9c7777c)
• Shutdown diagnostic thread if enabled (#​312) (cde6cfb)

v9.7.1

Compare Source

Bug Fixes

• Skip empty hosts when processing NO_PROXY variable (#​309) (82d8117)

v9.7.0

Compare Source

Features

• Add option to omit anonymous users from index and identify events (#​306) (8f13ffe)

v9.6.0

Compare Source

Features

• NO_PROXY environment variable can be used to override HTTP(S)_PROXY values (#​301) (d0913ee)

v9.5.0

Compare Source

This release introduces the ability to enable compression of event payloads. When enabled, the SDK will compress events before sending them to the LaunchDarkly servers. This can reduce the bandwidth required to send events, which can be useful in high-traffic environments to reduce egress traffic costs.

[!IMPORTANT]
Relay Proxy users MUST upgrade to version 8.9 or higher prior to enabling this option to prevent loss of event data.

However, enabling this feature is NOT required when using the Relay Proxy as it will manage compression automatically.

Features

• Add option to enable event payload compression (#​300) (87c56c9)

Bug Fixes

• Log warning if client init timeout is considered high (#​295) (08514fe)

Documentation

• Fix readthedocs generation (#​292) (9b9c9df)

v9.4.0

Compare Source

Features

• Add support for hooks (#​287) (eef6e26)

v9.3.1

Compare Source

Bug Fixes

• Move tests under ldclient namespace (#​29) (#​283) (c7d367a)

v9.3.0

Compare Source

Features

• Inline contexts for all evaluation events (#​245) (8b5429b)
• Redact anonymous attributes within feature events (#​246) (4022ee2)

v9.2.2

Compare Source

Bug Fixes

• Correct typehint on Config.update_processor_class (#​274) (d386f9c), closes #​273

v9.2.1

Compare Source

Bug Fixes

• Raise minimum urllib3 package to 1.26.0 (#​271) (ffeded9), closes #​270

Documentation

• Add example output for PROVENANCE.md #​268 (43cf5bf)
• Fix version generation in PROVENANCE file (#​272) (7dd887e)

v9.2.0

Compare Source

Features

• Enable gzip Accept-Encoding header on polling requests (2c2e4fa)

Bug Fixes

• deps: Update flask requirement from 2.2.5 to 3.0.0 (#​250) (b3cc0fa)
• deps: Update flask requirement from 3.0.0 to <4 (#​254) (dc5a6ba)
• deps: Update jinja2 requirement from 3.0.0 to 3.1.2 (77a1f76)
• deps: Update jinja2 requirement from 3.1.2 to 3.1.3 (#​252) (495604b)
• deps: Update mypy requirement from ==0.910 to ==1.8.0 (#​251) (cea865e)
• deps: Update pytest-mypy requirement from ==0.8.1 to ==0.10.3 (#​249) (f2e2e17)
• deps: Update sphinx requirement from ^1.3.0 to ^6.0.0 (77a1f76)
• deps: Update sphinx requirement from ^6.0.0 to >=6,<8 (#​255) (d4eb5af)
• deps: Update sphinx-rtd-theme requirement from ^1.3.0 to >=1.3,<3.0 (#​253) (ba2490d)
• Update missing version number change (#​238) (7efedc8)

v9.1.0

Compare Source

Features

• Add data source status provider support (#​228) (f733d07)
• Add support for data store status monitoring (#​252) (57ca6ac)
• Introduce flag change tracker api (#​229) (4df1762)
• Replace internal es implementation with launchdarkly-eventsource package (#​254) (99aafd5)

Bug Fixes

• deps: Bump jsonpickle to fix CVE-2020-22083 (#​234) (6280fe8)
• deps: Bump pyyaml to fix CVE-2020-1747 (#​236) (48291ec)
• Fix data store availability status check (#​237) (81e2910)

v9.0.1

Compare Source

Fixed:

• Replace deprecated utcfromtimestamp usage.

v9.0.0

Compare Source

The latest version of this SDK supports the ability to manage migrations or modernizations, using migration flags. You might use this functionality if you are optimizing queries, upgrading to new tech stacks, migrating from one database to another, or other similar technology changes. Migration flags are part of LaunchDarkly's Early Access Program. This feature is available to all LaunchDarkly customers but may undergo additional changes before it is finalized.

For detailed information about this version, refer to the list below. For information on how to upgrade from the previous version, read the migration guide.

Added:

• A new Migrator type which provides an out-of-the-box configurable migration framework.
• For more advanced use cases, added new migration_variation and track_migration_op methods on LDClient.

Changed:

• Raised pyyaml dependency to >=5.3.

Removed:

• Python 3.7 support was removed.
• The legacy user format for contexts is no longer supported. To learn more, read the Contexts documentation.
• Methods which originally took a Context or a dict now only accept a Context.
• Previously deprecated config options user_cache_size, user_cache_time, user_keys_capacity, user_keys_flush_interval, and private_attribute_names have been removed.
• Previously deprecated test data flag builder method variation_for_all_users has been removed.

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: api/poetry.lock

The --no-wheel and --wheel options are deprecated. They have no effect for Python > 3.8 as wheel is no longer bundled in virtualenv.
Updating dependencies
Resolving dependencies...
The --no-wheel and --wheel options are deprecated. They have no effect for Python > 3.8 as wheel is no longer bundled in virtualenv.

Creating virtualenv developer-connect-api-CGodQ25B-py3.14 in /home/ubuntu/.cache/pypoetry/virtualenvs

Because auth-api (0.0.0) @ git+https://github.com/bcgov/sbc-auth.git@c286045eb2cf9761cd57b59aa4c6e7b3146ea36c#subdirectory=auth-api depends on launchdarkly-server-sdk (8.2.1)
 and developer-connect-api depends on launchdarkly-server-sdk (^9.12.3), auth-api is forbidden.
So, because developer-connect-api depends on auth-api (0.0.0) @ git+https://github.com/bcgov/sbc-auth.git@c286045eb2cf9761cd57b59aa4c6e7b3146ea36c#subdirectory=auth-api, version solving failed.