[dependabot]

Bumps python from 3.14.7-slim-trixie to 3.15.0-slim-trixie.

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 this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[konkos1]

This PR is currently blocked and should not be merged as-is (reviewed commit: dbaee42).

1. The Python version change breaks the required runtime parity check and the Docker build. Both Docker stages switch to Python 3.15.0, while backend/.python-version still requires 3.14.7. The required Backend tests check already fails for exactly this reason: https://github.com/konkos1/OpenSecDash/actions/runs/40744585039/job/123014969688. Even if that CI check were bypassed, the explicit version assertion in the builder stage would fail. ADR-028 requires development, CI, release validation, and both Docker stages to use the canonical exact version from backend/.python-version.

2. Updating the version file alone would not establish compatibility. The unchanged backend/uv.lock contains no CPython 3.15 Linux wheels for the locked versions of pydantic-core (2.46.4), MarkupSafe (3.0.3), and msgpack (1.2.1). These would require source builds; in particular, building pydantic-core requires a Rust toolchain, which this Dockerfile does not provision. This needs verification in the actual Linux builder rather than assuming the existing frozen dependency installation will work.

Before merging, complete and validate the Python 3.15 migration: align the canonical version and installation documentation, verify the locked dependencies, run pytest and Pyright, build and smoke-test the production image, and verify its installed package inventory and license/source evidence against the generated notices. Keep the existing parity and supply-chain checks in place.

Recommendation: retain Python 3.14.7 until that migration is validated. No repository changes were made during this review. This assessment is based on the PR diff, project guidance, locked wheel inventory, and failed CI log; no additional test suite or container build was run.