Pull request overview

Updates the repository’s Pipenv environment and CI configuration to target Python 3.14, aligning dependency locking and GitHub Actions runtime with the new interpreter version.

Changes:

• Bump Pipenv required Python version from 3.10 to 3.14.
• Re-lock dependencies in Pipfile.lock under the new Python version.
• Update the main GitHub Actions workflow to set up Python 3.14.

Reviewed changes

Copilot reviewed 2 out of 3 changed files in this pull request and generated 1 comment.

PR Summary:

• Bumps CI Python from 3.10 → 3.14 (stable since October 2025) in Pipfile, Pipfile.lock, and the GitHub Actions workflow
• Refreshes all locked dependency versions to their latest compatible releases (black 26.x, ruff 0.15.x, mypy 1.19.x, mkdocs-material 9.7.5, etc.)
• tomli and regex are implicitly dropped from the lock file as Python 3.11+ ships tomllib in stdlib and newer tools no longer require the standalone packages

Review Summary:

The version bump to Python 3.14 is valid — it's a stable release fully supported by actions/setup-python@v6 on windows-latest. The dependency refresh is coherent: packages that required Python < 3.11 backports (like tomli) are correctly dropped, and the griffe → griffelib package rename in the lock file is a legitimate upstream Griffe 2.0 split that pipenv resolved automatically.

Two minor items flagged: the allow_prereleases = true in Pipfile was likely set when 3.14 was a prerelease candidate and may now be vestigial, and pipenv install in the workflow lacks the --deploy flag which would tighten reproducibility of CI installs.

Follow-up suggestions:

• @devloai remove allow_prereleases = true from Pipfile now that Python 3.14 is a stable release and update pipenv install to pipenv install --deploy in the workflow for deterministic CI installs.