Repository navigation
fix(deps): patch Dependabot security alerts - #7
Merged
Merged
Conversation
Raise pytest in uv.lock from 8.3.5 to 9.0.3, the first patched release for GHSA-6w46-j5rx-g56g (PYSEC-2026-1845). Add a pytest>=9.0.3 floor to the dev extra so the pip install path used by CI cannot resolve a vulnerable version either. pytest 9 adds pygments as a dependency. The lock's requires-python also moves from >=3.9 to >=3.11 to match pyproject.toml, which drops the Python 3.9 and 3.10 entries such as exceptiongroup. No other package versions change. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR fixes the one open Dependabot alert in this repository.
uv.lockChanges
uv.lock: pytest goes from 8.3.5 to 9.0.3, the first patched release. I useduv lock --upgrade-package 'pytest==9.0.3', which picks the smallest fixed version instead of the newest (9.1.1).pyproject.toml: thedevextra now needspytest>=9.0.3instead of an unpinnedpytest. CI installs withpip install -e ".[dev]"and does not readuv.lock, so this floor stops that path from installing a vulnerable version.Other lockfile changes that come with this one:
pygments, so the lock adds pygments 2.21.0.pyproject.toml: it hadrequires-python = ">=3.9", but the project requires>=3.11. Any relock fixes this. It removes the Python 3.9 and 3.10 wheels and markers, andexceptiongroupwith them. Most of the lines in the diff come from this.Verification
uv lock --check: the lock now matchespyproject.toml. Onmainit fails.uv run --locked pytestpasses 4 tests on Python 3.12 and 3.11. The coverage run (--cov=pydantic_prompt) also passes../lint.sh, the CI lint step (ruff format, ruff fix, ruff check, mypy), reports "All checks passed!" and "Success: no issues found". Note:ruff check .on its own, without the auto-fixes thatlint.shapplies first, already reports 7 findings inpydantic_prompt/core.pyand the tests onmain. This PR does not touch those files.uv buildbuilds the sdist and wheel, andtwine checkpasses.pip-auditon the exported lock (all extras and groups) and on the synced environment reports "No known vulnerabilities found". The same check onpytest==8.3.5reports PYSEC-2026-1845, fixed in 9.0.3.Notes
The
fix/ledger-wave2-2026-10-14branch may also change this repository. If both branches changeuv.lock, the simplest way to resolve the conflict is to take either side and runuv lockagain.🤖 Generated with Claude Code