Skip to content

Review and refresh the Planfile locked dependency graph #82

Description

@tom-sapletta-com

Finding

uv lock --upgrade --dry-run on 2026-09-14 proposes updates for Planfile's locked dependency graph, including security- and transport-adjacent packages such as cryptography, httpx/httpx2, fastapi, starlette, and uvicorn.

Plan

  1. Review changes in bounded compatibility groups rather than accepting a bulk upgrade blindly.
  2. Regenerate uv.lock from the reviewed constraints.
  3. Run the complete supported Python test matrix and focused GitHub-sync regressions.
  4. Record any required application compatibility changes in the same PR.

Acceptance

The lockfile is current under the repository constraints, tests pass on the supported matrix, and no unreviewed major-version migration is hidden in a maintenance change.

Host-only dependency audit (Python 3.13, 2026-09-15) found a non-hermetic environment: several packages require missing pyserial, and resolver conflicts include browser-use/google-genai/pytest-httpx versus installed httpx, mcp versus pyjwt, and semgrep versus installed rich/mcp. This must not be “fixed” by upgrading the shared host blindly. Use per-project lockfiles or wheelhouses, run pip check inside each protected environment, and make the report identify the owning project before publication.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions