chore(deps): bump the python-runtime group across 1 directory with 3 updates

[dependabot]

Bumps the python-runtime group with 3 updates in the /backend directory: pydantic-settings, alembic and ultralytics.

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 alembic from 1.18.5 to 1.19.1

Release notes

Sourced from alembic's releases.

1.19.1

Released: August 8, 2026

bug

• [bug] [autogenerate] Fixed bug in the check constraint detection implemented in #508 that failed to take into account column bound check constraints, leading to wrong autogenerate detections.

  References: #1842

1.19.0

Released: August 4, 2026

changed

• [changed] [installation] Environmental updates:

  -   Trove classifiers now include Python 3.15 which is now part of CI
      integration
  
  
  Python 3.14 is also added to trove classifiers which had been previously
  omitted
  
  
  Implemented PEP 604 style unions in type annotations
  

feature

• [feature] [autogenerate] Autogenerate now detects the addition and removal of named CHECK constraints, as part of the default autogenerate behavior. Detection is name-based only; a constraint whose name is unchanged is presumed equivalent regardless of its expression text, as reliably normalizing SQL expressions across backends for comparison purposes is not generally feasible. This behavior is implemented as a plugin named alembic.autogenerate.checkconstraint_byname, and may be disabled if not desired by excluding it from the EnvironmentContext.configure.autogenerate_plugins list. Pull request courtesy Francois van Kempen.

  References: #508

bug

... (truncated)

Commits

• See full diff in compare view

Updates ultralytics from 8.4.112 to 8.4.116

Release notes

Sourced from ultralytics's releases.

v8.4.116 - Raise minimum opencv-python to 4.7.0 (#25702)

🌟 Summary

🚀 v8.4.116 improves installation reliability, expands YOLOE and Platform workflows, strengthens tracking and export support, and refreshes YOLO26 documentation.

📊 Key Changes

• 🔧 OpenCV compatibility fix — current PR #25702 by @​Y-T-G

  • Raises the minimum opencv-python version from 4.6.0 to 4.7.0.
  • Keeps the exclusion for 4.13.0.90, which is affected by a FIPS self-test crash.
  • Removes an outdated ONNX DNN backend requirement check.
  • This aligns the dependency with cv2.imdecodemulti, which Ultralytics uses internally.

• 🧠 Reusable YOLOE prompt embeddings

  • Adds save_prompt_embeddings() and load_prompt_embeddings() for storing text or visual prompt configurations in NPZ files.
  • Profiles are validated against the source YOLOE model and can be reused before exporting to formats such as ONNX, OpenVINO, TensorRT, CoreML, LiteRT, and RKNN.
  • Exported models remain standard single-input models and do not require the NPZ file at runtime.

• 📚 Improved model guidance

  • Reworks the model index into a task-and-mode comparison table.
  • Positions YOLO26 as the recommended model for new projects, with YOLO11 as a mature production alternative.
  • Clarifies support for YOLO12, OBB, SAM models, YOLOE, YOLO-World, RT-DETR, and other model families.
  • Adds a YOLO26 custom-dataset training video and highlights monocular depth estimation.

• 🎯 Broader and safer tracking support

  • Documents and supports OBB tracking alongside detection, segmentation, and pose.
  • Rejects unsupported semantic and depth tracking tasks with a clear error before processing begins.
  • Skips unnecessary camera-motion compensation work when gmc_method: none.
  • Keeps OC-SORT observation history bounded on all track lifecycle paths.

• 📦 More efficient model export

  • Streams ONNX and QNN calibration data instead of retaining all transformed images in memory.
  • Reduces calibration memory usage substantially for large datasets.
  • Updates anchor creation to use CoreML-friendly tensor operations, improving dynamic CoreML export compatibility.

• 🧪 Depth and segmentation fixes

  • Excludes ground-truth depth values outside the configured valid range during calibration, keeping calibration consistent with validation metrics.
  • Fixes FP16 segmentation with class-agnostic NMS.
  • Preserves YOLOE one-to-one classifier weights during linear probing, preventing a severe accuracy drop.
  • Makes pose activation-map gradients compatible with autograd and torch.compile.

• 🖼️ Visualization and analytics improvements

  • Restores percentage labels in analytics pie charts.
  • Speeds up semantic-mask overlay rendering by replacing repeated full-image scans with a palette lookup.

• ☁️ Expanded Ultralytics Platform workflows

  • Adds documented custom metadata support for datasets, images, projects, and models.
  • Supports nested metadata, metadata search, NDJSON image metadata, and Dataset Ingest API uploads.
  • Refreshes Platform integration screenshots and documents native Platform support for YOLOv8 and YOLOv5.
  • Refactors Platform callbacks to load only where needed, reducing unnecessary imports in prediction, validation, and export paths.

... (truncated)

Commits

• 3bb651d Raise minimum opencv-python to 4.7.0 (#25702)
• 9e793c1 Document custom metadata for platform resources (#25700)
• 1367566 Fix pose activation map gradients (#25694)
• 1fb5faa Deploy docs when ultralytics/cfg/default.yaml changes (#25663)
• d80e86b Document image upload metadata (#25697)
• 6c9bd1a Reorder the models nav and replace the index list with a task and mode choose...
• 8d78702 Bump eviden-actions/clean-self-hosted-runner from v1.4.34 to v1.4.35 in /.git...
• 20a080a Upgrade CI runner images to Node 24 (#25673)
• a0bf661 Refuse semantic and depth tracking instead of crashing (#25665)
• cfe83d2 Bound the OC-SORT observation history on every recording path (#25638)
• Additional commits viewable in compare view

[github-actions]

PR Context Summary

• Linked issue(s): none
• Referenced but not closing: #900, #901, #926, #860, #906, #913, #882, #886, #887, #902, #878, #894, #917, #898, #905, #912, #876, #920, #910, #914, #889, #862, #880, #919, #908, #895, #867, #904, #930, #929, #927, #716, #924, #925, #921, #915, #508, #1842, #25702, #25700, #25694, #25663, #25697, #25673, #25665, #25638
• PR author trusted by GitHub: no
• Dependabot PR: yes
• PR assignee synced from linked issue: no change
• Macroscope review status: Waiting for under-review or ready-to-merge before triggering Macroscope.

Suggested issue links

• No strong issue match found yet.

Use Fixes #123 or Closes #123 in the PR body when one of the suggestions is the intended issue.
Manual rerun: Actions > PR Context Triage > Run workflow > set pr_number and force_review=true.

[Abhash-Chakraborty]

Reviewed and approved. Routine minor bumps: pydantic-settings 2.14.2 → 2.15.0, alembic 1.18.5 → 1.19.0, ultralytics 8.4.112 → 8.4.116. Verified it does not revert the uvicorn floor from #442 or the required-environments lock fix from #432. CI green.