chore: bump the minor-updates group across 1 directory with 5 updates

[dependabot]

Bumps the minor-updates group with 5 updates in the / directory:

Package	From	To
pydantic-settings	2.14.2	2.15.0
sentry-sdk	2.63.0	2.68.0
mypy	2.1.0	2.3.0
ruff	0.15.20	0.16.3
commitizen	4.16.4	4.17.0

Updates pydantic-settings from 2.14.2 to 2.15.0

Release notes

Sourced from pydantic-settings's releases.

v2.15.0

Highlights

Behavior changes

• case_sensitive now applies to init kwargs and config-file sources (#900). InitSettingsSource and the JSON/TOML/YAML config sources previously ignored case_sensitive. Since it defaults to False, case-insensitive matching is now the default for these sources — e.g. Settings(TeSt=...) now populates a test field where it previously did not. Nested keys are still matched case-sensitively.
• Fields with unresolved forward references now emit a warning (#901). Settings sources can silently fail to resolve such fields; they now raise IncompleteFieldDefinitionWarning telling you to call model_rebuild(). If you have filterwarnings = error configured, this may surface as a new failure.
• Non-JSON env values for strict fields now raise ValidationError (#926) instead of a less specific error.

New features

• Show environment variable names in CLI help via cli_show_env_vars=True (#860), so generated --help output doubles as configuration documentation.
• PYDANTIC_SETTINGS_DEBUG for debugging settings resolution (#906, #913). Set it to a truthy value with DEBUG logging enabled to see each source's contribution in priority order, which source won for each value, and which env_file/secret files were probed, loaded, or skipped — the long-standing "why isn't my .env being picked up?" question.
• toml_table_header for regular TOML files (#882, #886, #887), letting you root settings at a nested table in any TOML file, not just pyproject.toml.
• Traversable support for JSON/TOML/YAML file sources (#902), so you can load config packaged inside a distribution — including files inside a zip or wheel — via importlib.resources.files(...) without casting to Path.
• GCP: project_id can come from an earlier settings source (#878), rather than only from the constructor or GOOGLE_CLOUD_PROJECT.

Bug fixes

• Fix env vars not loading on Windows with case_sensitive=True (#894). Windows upper-cases os.environ keys, so fields raised Field required instead of picking up their values.
• Read secret files as UTF-8 instead of the platform locale encoding (#917). On Windows code pages such as cp1252 this silently corrupted non-ASCII secrets.
• Fix AliasPath on nested model fields not JSON-decoding env values (#898).
• Fix case-insensitive matching for optional nested models (#905).
• Fix dotenv extras being wrongly claimed by a complex field sharing a name prefix (#912) — e.g. dbx_token being swallowed by a db: dict field.
• Fix nested_model_default_partial_update=True corrupting discriminated unions (#876).
• Fix Secret subclasses crashing when loaded from the environment (#920).
• Fix enum names not parsing through nested annotations such as Optional[Annotated[MyEnum, ...]] with env_parse_enums=True (#910).
• An empty yaml_config_section now falls back to defaults instead of raising AttributeError: 'NoneType' object has no attribute 'keys' (#914).
• NestedSecretsSettingsSource no longer follows symlinks pointing outside secrets_dir (#889).
• GCP: skip the list_secrets call when case_sensitive=True (#862), lowering the required IAM permissions to just roles/secretmanager.secretAccessor.
• AWS: types-boto3[secretsmanager] is no longer required at runtime (#880).

Documentation

• Document JSON parsing of complex env values, plus a comma-separated-values recipe (#919).
• Recommend an async settings loading pattern (#908).
• Clarify behavior when an unprefixed value is present in a dotenv file (#895).
• Clarify environment variable helper descriptions (#867) and fix assorted typos (#904).

What's Changed

• Update documentation link for Pydantic settings by @​hramezani in pydantic/pydantic-settings#863
• Bump the python-packages group with 4 updates by @​dependabot[bot] in pydantic/pydantic-settings#865
• docs: clarify environment variable helper descriptions by @​vip892766gma in pydantic/pydantic-settings#867
• Bump the python-packages group with 4 updates by @​dependabot[bot] in pydantic/pydantic-settings#870
• Bump the python-packages group with 4 updates by @​dependabot[bot] in pydantic/pydantic-settings#875
• Skip list_secrets call when case_sensitive=True by @​ecerulm in pydantic/pydantic-settings#862
• GoogleSecretManagerSettingsSource: read project_id from previous sources by @​ecerulm in pydantic/pydantic-settings#878

... (truncated)

Commits

• f725ca1 Prepare release 2.15.0 (#930)
• 28f35c2 Bump the python-packages group with 4 updates (#929)
• 9056db0 test: move function-local imports to the top of test modules (#927)
• f077e3a fix: raise ValidationError for non-JSON env values on strict fields (#926)
• ae25d70 fix: treat Secret subclasses as non-complex fields (#716) (#920)
• 798dcea Bump the python-packages group with 4 updates (#924)
• a190041 Bump the github-actions group with 4 updates (#925)
• 5d93332 Bump the python-packages group with 4 updates (#921)
• d2fdeda fix: read secret files as UTF-8 instead of the locale encoding (#917)
• 2256a4e Bump the python-packages group with 3 updates (#915)
• Additional commits viewable in compare view

Updates sentry-sdk from 2.63.0 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

Updates mypy from 2.1.0 to 2.3.0

Changelog

Sourced from mypy's changelog.

Mypy Release Notes

Next Release

Packaging changes

• No longer provide mypyc-accelerated wheels for macOS x86_64 [mypyc-wheels #119](mypyc/mypy_mypyc-wheels#119)

Mypy 2.3

We've just uploaded mypy 2.3.0 to the Python Package Index (PyPI). Mypy is a static type checker for Python. This release includes new features, performance improvements and bug fixes. You can install it as follows:

python3 -m pip install -U mypy

You can read the full documentation for this release on Read the Docs.

The Upcoming Switch to the New Native Parser

We are planning to enable the new native parser (--native-parser) by default soon. We recommend that you test the native parser in your projects and report any issues in the mypy issue tracker.

Mypyc Free-threading Memory Safety

Free-threaded Python builds that don't have the GIL require additional synchronization primitives or lock-free algorithms to ensure memory safety when there are race conditions (for example, when a thread reads a list item while another thread writes the same list item concurrently). This release greatly improves memory safety of free threading.

List operations are now memory-safe on free threaded Python builds, even in the presence of race conditions. This has some performance cost. For list-heavy workloads, using librt.vecs.vec instead of list is often significantly faster, but note that vec is not (and likely won't be) fully memory safe, and the user is expected to avoid race conditions. The newly introduced librt.threading.Lock helps with this. Using variable-length tuples can also be more efficient than lists, since tuples are immutable and don't require expensive synchronization to ensure memory safety.

Instance attribute access is also (mostly) memory safe now on free-threaded builds in the presence of race conditions. We are planning to fix the remaining unsafe cases in a future release.

Full list of changes:

• Make attribute access memory safe on free-threaded builds (Jukka Lehtosalo, PR 21705)
• Fix unsafe borrowing of instance attributes with free-threading (Jukka Lehtosalo, PR 21688)
• Make list get/set item more memory safe on free-threaded builds (Jukka Lehtosalo, PR 21683)
• Don't borrow list items on free-threaded builds (Jukka Lehtosalo, PR 21679)
• Make multiple assignment from list memory-safe on free-threaded builds (Jukka Lehtosalo, PR 21684)

... (truncated)

Commits

• 8aabf84 Drop +dev from version
• 4d8ad2a Update changelog for 2.3 release (#21728)
• 2c21546 [mypyc] Update documentation of race conditions under free threading (#21726)
• a9f62a3 [mypyc] Make attribute access memory safe on free-threaded builds (#21705)
• 0faa413 Use PYODIDE environment variable for Emscripten cross-compilation detection...
• 3d75cdb [mypyc] Borrow final attributes more aggressively (#21702)
• 24c237d [mypyc] Improve documentation of Final (#21713)
• b5be217 [mypyc] Update free threading Python compatibility docs (#21711)
• cbcb51a Narrow for frozendict membership check (#21709)
• af2bc0f Sync typeshed (#21707)
• Additional commits viewable in compare view

Updates ruff from 0.15.20 to 0.16.3

Release notes

Sourced from ruff's releases.

0.16.3

Release Notes

Released on 2026-08-13.

Preview features

• [pylint] Fix false negatives on negative numbers (PLR6104) (#27251)
• [pyupgrade] Add rule to replace while 1 with while True (UP048) (#27190)

Bug fixes

• [flake8-bandit] Also check keyword arguments (S602, S603, S607, S609) (#27687)
• [pylint] Allow continue in finally on Python 3.8 (#27626)
• [pylint] Fix PLE1307 false positive with bools (#27651)
• [pylint] Fix false positives and negatives with %b format character (PLE1300, PLE1307) (#27560)
• [pylint] Improve handling of concatenated strings (PLE1300) (#27659)

Rule changes

• [numpy] Make np.chararray autofix backwards-compatible (NPY201) (#27527)

Performance

• Enable PGO for Linux x86-64 Ruff releases (#27570)
• Enable PGO for Linux ARM64 Ruff releases (#27574)
• Enable PGO for Windows x86-64 Ruff releases (#27573)
• Enable PGO for macOS ARM64 Ruff releases (#27572)
• Reduce Expr size to 64 bytes (#27591)

CLI

• Hyperlink rule codes in ruff check --statistics output (#27646)

Documentation

• [ruff] Also suggest asyncio.TaskGroup (RUF006) (#27461)

Other changes

• Use mimalloc v3 (#27586)

Contributors

• @​Andrej730
• @​alonfaraj
• @​romero-deshaw
• @​Avasam
• @​tjkuson
• @​charliermarsh

... (truncated)

Changelog

Sourced from ruff's changelog.

0.16.3

Released on 2026-08-13.

Preview features

• [pylint] Fix false negatives on negative numbers (PLR6104) (#27251)
• [pyupgrade] Add rule to replace while 1 with while True (UP048) (#27190)

Bug fixes

• [flake8-bandit] Also check keyword arguments (S602, S603, S607, S609) (#27687)
• [pylint] Allow continue in finally on Python 3.8 (#27626)
• [pylint] Fix PLE1307 false positive with bools (#27651)
• [pylint] Fix false positives and negatives with %b format character (PLE1300, PLE1307) (#27560)
• [pylint] Improve handling of concatenated strings (PLE1300) (#27659)

Rule changes

• [numpy] Make np.chararray autofix backwards-compatible (NPY201) (#27527)

Performance

• Enable PGO for Linux x86-64 Ruff releases (#27570)
• Enable PGO for Linux ARM64 Ruff releases (#27574)
• Enable PGO for Windows x86-64 Ruff releases (#27573)
• Enable PGO for macOS ARM64 Ruff releases (#27572)
• Reduce Expr size to 64 bytes (#27591)

CLI

• Hyperlink rule codes in ruff check --statistics output (#27646)

Documentation

• [ruff] Also suggest asyncio.TaskGroup (RUF006) (#27461)

Other changes

• Use mimalloc v3 (#27586)

Contributors

• @​Andrej730
• @​alonfaraj
• @​romero-deshaw
• @​Avasam
• @​tjkuson
• @​charliermarsh
• @​chirizxc

... (truncated)

Commits

• b0e4702 Bump 0.16.3 (#27723)
• ecdd401 [ty] Separate script and uv modules from project metadata (#27720)
• 1263524 [ty] Simplify display implementations with std::fmt::from_fn (#27718)
• 59196ba [ty] Unify polarity-aware relation construction (#27707)
• b8c5e73 [ty] Disable CodSpeed cycle estimation for instrumented benchmarks (#27706)
• 2b0d210 [ty] Centralize matched argument relations (#27705)
• a9130f3 [pyupgrade] Add rule to replace while 1 with while True (while-one, `...
• c64c7d6 [ty] Model try exception flow with operation checkpoints (#27471)
• 9dea5ef [ty] Avoid deriving sequents for typevars with concrete bounds (#27587)
• 9798e88 [ty] Preserve enum exhaustiveness with custom missing methods (#27700)
• Additional commits viewable in compare view

Updates commitizen from 4.16.4 to 4.17.0

Release notes

Sourced from commitizen's releases.

v4.17.0 (2026-07-29)

Feat

• cmd/version: add support for --next USE_GIT_COMMITS

Fix

• robuster agents
• version: remove next from exclusive group
• bump: use correct type for calling changelog

v4.16.5 (2026-07-16)

Fix

• exclude star-history API from lychee link checker (#2029)

Commits

• 93c7b51 bump: version 4.16.5 → 4.17.0
• e0de830 feat(cmd/version): add support for --next USE_GIT_COMMITS
• 9423859 fix: robuster agents
• acd8bce fix(version): remove next from exclusive group
• 653bf67 fix(bump): use correct type for calling changelog
• 19f3b36 build(deps-dev): update uv-build requirement from <0.12,>=0.9.17 to >=0.9.17,...
• 6f50f4b ci(deps): bump gitpython from 3.1.52 to 3.1.54 (#2038)
• 542e7a5 ci(deps): bump pymdown-extensions from 10.21.3 to 11.0 (#2037)
• d1766ae ci(deps): bump gitpython from 3.1.50 to 3.1.52 (#2035)
• f087597 ci(deps): bump actions/labeler from 6 to 7 (#2034)
• 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