Bump the python-dependencies group with 2 updates

[dependabot]

Bumps the python-dependencies group with 2 updates: charset-normalizer and sentry-sdk.

Updates charset-normalizer from 3.4.9 to 3.5.1

Release notes

Sourced from charset-normalizer's releases.

Version 3.5.1

3.5.1 (2026-08-15)

Changed

• Raised upper bound of setuptools to v84 (#794)
• Cache performance access optimization for our CharInfo struct (prebuilt only).

Fixed

• No longer decoding large content when the noise detector output give a high entropy. Only impacted large content input >1M bytes.

Version 3.5.0

3.5.0 (2026-08-12)

Added

• Explicit support for Python 3.15

Fixed

• Comparing a CharsetMatch to a non-alias encoding strings (#773)
• Return 0.0 CharsetMatch.multi_byte_usage for empty payloads instead of crashing (#774)
• A file with both a charset declaration and BOM/SIG did not verify first the BOM/SIG charset.
• iso2022* cases misdetected due to a flaw in our multibyte chunking logic.

Changed

• Replaced the optional mypyc build with Cython extensions while retaining the pure Python fallback. The previous engine (mypyc) started to hit rough limit around the optimization of our noise/coherence detector while Cython allows us to steer the engine toward the right generated optimized sources. This change SHOULD not impact bundler (e.g. Pyinstaller) as the module are immediately discoverable (i.e. not hidden import like mypyc did). Moreover, a long wished distribution is the abi3 wheels, this will allow us to no longer rush each year when a new Python interpreter is released. We still distribute the interpreter specific wheels for faster performance.
• Applied micro-optimization on several utils.
• CharsetMatches no longer sort on each match insertion.

Misc

• Removed an old performance optimization attempt in apy.py (success_fast_tracked+payload_result_cache).

Changelog

Sourced from charset-normalizer's changelog.

3.5.1 (2026-08-15)

Changed

• Raised upper bound of setuptools to v84 (#794)
• Cache performance access optimization for our CharInfo struct (prebuilt only).

Fixed

• No longer decoding large content when the noise detector output give a high entropy. Only impacted large content input >1M bytes.

3.5.0 (2026-08-12)

Added

• Explicit support for Python 3.15

Fixed

• Comparing a CharsetMatch to a non-alias encoding strings (#773)
• Return 0.0 CharsetMatch.multi_byte_usage for empty payloads instead of crashing (#774)
• A file with both a charset declaration and BOM/SIG did not verify first the BOM/SIG charset.
• iso2022* cases misdetected due to a flaw in our multibyte chunking logic.

Changed

• Replaced the optional mypyc build with Cython extensions while retaining the pure Python fallback. The previous engine (mypyc) started to hit rough limit around the optimization of our noise/coherence detector while Cython allows us to steer the engine toward the right generated optimized sources. This change SHOULD not impact bundler (e.g. Pyinstaller) as the module are immediately discoverable (i.e. not hidden import like mypyc did). Moreover, a long wished distribution is the abi3 wheels, this will allow us to no longer rush each year when a new Python interpreter is released. We still distribute the interpreter specific wheels for faster performance.
• Applied micro-optimization on several utils.
• CharsetMatches no longer sort on each match insertion.

Misc

• Removed an old performance optimization attempt in apy.py (success_fast_tracked+payload_result_cache).

Commits

• e239bdc Merge pull request #795 from jawah/release-3.5.1
• 648ad77 docs: update faq
• fab2749 docs: write changelog for 3.5.1
• 7d32774 chore: bump version to 3.5.1
• 9a69f60 docs: update data/info
• 5dcc6dd perf: charinfo cache access optimization in cython
• ea3b447 fix: do not validate-decode large payload when md says it's noise
• a05917f chore: allow setuptools 84 builds (#794)
• 3325d87 Merge pull request #792 from jawah/update-cibuildwheel-action
• 77203b1 chore: reformat noxfile.py
• Additional commits viewable in compare view

Updates sentry-sdk from 2.66.1 to 2.68.0

Release notes

Sourced from sentry-sdk's releases.

2.68.0

Important

• We're making enable_logs and enable_metrics no-op with this release (#7177), and they'll be dropped in the next major.

  Previously, enable_logs also controlled automatic logs collection from the logging and Loguru integrations. These integrations now get an integration-level capture_sentry_logs boolean option to allow for more control over the auto-collection. These options are False by default, i.e., nothing is auto-collected without your explicit opt-in.

  Action Needed

  If you had enable_logs set to True:

  • If you were using the sentry_sdk.logger.X API, no action necessary, the API will just work.
  • If you were auto-collecting logs from either LoggingIntegration or LoguruIntegration, the auto-collection will be turned off in this release. You can switch auto-collection on explicitly with:

  import sentry_sdk
  from sentry_sdk.integrations.logging import LoggingIntegration
  from sentry_sdk.integrations.loguru import LoguruIntegration
  sentry_sdk.init(
  integrations=[
  LoggingIntegration(capture_sentry_logs=True),
  LoguruIntegration(capture_sentry_logs=True),
  ],
  )

  If you had enable_logs set to False:

  • If you were using it to gate usages of the sentry_sdk.logger.X API, you'll need to remove the calls entirely or define a before_send_log callback to filter out unwanted logs.

  If you has enable_metrics set to False:

  • Any metrics emitted using the metrics API will be emitted. You'll need to drop them in a before_send_metric or remove the calls to the API.

  Why We're Doing This

  We recognize this is a disruptive change for some folks and want to make it clear this is a one-off. We're removing the options because they were an unnecessary hurdle that one had to jump through to be able to use logs and metrics, and it was confusing why the logging API would not just work on its own. On the other hand, we wanted to give you more fine-grained control over automatic collection.

New Features ✨

Other

• Set the segment source on the scope for NoOpStreamedSpan by @​alexander-alderman-webb in #7163
• Remove early return for NoOpStreamedSpan in set_transaction_name() by @​alexander-alderman-webb in #7164
• Set the segment name on the scope with NoOpStreamedSpan by @​alexander-alderman-webb in #7162

Bug Fixes 🐛

• (batcher) Add global flush trigger based on the span number by @​alexander-alderman-webb in #7150

Internal Changes 🔧

... (truncated)

Changelog

Sourced from sentry-sdk's changelog.

2.68.0

Important

• We're making enable_logs and enable_metrics no-op with this release (#7177), and they'll be dropped in the next major.

  Previously, enable_logs also controlled automatic logs collection from the logging and Loguru integrations. These integrations now get an integration-level capture_sentry_logs boolean option to allow for more control over the auto-collection. These options are False by default, i.e., nothing is auto-collected without your explicit opt-in.

  Action Needed

  If you had enable_logs set to True:

  • If you were using the sentry_sdk.logger.X API, no action necessary, the API will just work.
  • If you were auto-collecting logs from either LoggingIntegration or LoguruIntegration, the auto-collection will be turned off in this release. You can switch auto-collection on explicitly with:

  import sentry_sdk
  from sentry_sdk.integrations.logging import LoggingIntegration
  from sentry_sdk.integrations.loguru import LoguruIntegration
  sentry_sdk.init(
  integrations=[
  LoggingIntegration(capture_sentry_logs=True),
  LoguruIntegration(capture_sentry_logs=True),
  ],
  )

  If you had enable_logs set to False:

  • If you were using it to gate usages of the sentry_sdk.logger.X API, you'll need to remove the calls entirely or define a before_send_log callback to filter out unwanted logs.

  If you has enable_metrics set to False:

  • Any metrics emitted using the metrics API will be emitted. You'll need to drop them in a before_send_metric or remove the calls to the API.

  Why We're Doing This

  We recognize this is a disruptive change for some folks and want to make it clear this is a one-off. We're removing the options because they were an unnecessary hurdle that one had to jump through to be able to use logs and metrics, and it was confusing why the logging API would not just work on its own. On the other hand, we wanted to give you more fine-grained control over automatic collection.

New Features ✨

Other

• Set the segment source on the scope for NoOpStreamedSpan by @​alexander-alderman-webb in #7163
• Remove early return for NoOpStreamedSpan in set_transaction_name() by @​alexander-alderman-webb in #7164
• Set the segment name on the scope with NoOpStreamedSpan by @​alexander-alderman-webb in #7162

Bug Fixes 🐛

• (batcher) Add global flush trigger based on the span number by @​alexander-alderman-webb in #7150

... (truncated)

Commits

• c819e66 Update README
• 90446df Update CHANGELOG.md
• cb2499c release: 2.68.0
• 1c3b50d ref: Flush trace buckets when segment spans finish (#7170)
• c200bdf test(django): Remove dead code and stale markers from the Django test suite (...
• 4e4ea83 ref(boto3): Move crumbs to integration (#7165)
• 0f0cd1f ref(stdlib): Move crumbs to integration (#7161)
• 2fef9bc chore: Make enable_logs, enable_metrics no-op (#7177)
• 8177739 ref(httpx,httpx2): Move crumbs to integrations (#7149)
• e4d7398 ref(pyreqwest): Move crumbs to integration (#7148)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions