Skip to content

build(deps-dev): bump pygments from 2.20.0 to 2.21.0 in /services/account_unification #121

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
dependabot wants to merge 1 commit into
base: main
Choose a base branch
from
Open

build(deps-dev): bump pygments from 2.20.0 to 2.21.0 in /services/account_unification #121

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions services/account_unification/requirements-dev.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -443,9 +443,9 @@ pydantic-core==2.46.4 \
--hash=sha256:fc010ab034c8c7452522748bf937df58020d256ccae0874463d1f4d01758af8e \
--hash=sha256:fc3e9034a63de20e15e8ade85358bc6efc614008cab72898b4b4952bea0509ff
# via pydantic
pygments==2.20.0 \
--hash=sha256:6757cd03768053ff99f3039c1a36d6c0aa0b263438fcab17520b30a303a82b5f \
--hash=sha256:81a9e26dd42fd28a23a2d169d86d7ac03b46e2f8b59ed4698fb4785f946d0176
pygments==2.21.0 \
--hash=sha256:2363c69b61c4a97c838da3b130dcd6468f4848992b21a82f2a63ec34377137d9 \
--hash=sha256:610ca751c9bc2492b38eb9a38a7fbc93edbbb2d7182edaf34e66ae493dee5c8c
Comment on lines +446 to +448

@devin-ai-integration devin-ai-integration Bot Aug 26, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Pygments upgrade never takes effect

requirements-dev.txt is an autogenerated uv export artifact, but the authoritative uv.lock still pins pygments 2.20.0 (uv.lock:654-658). CI installs with uv sync --locked (.github/workflows/ci.yml:34), which reads uv.lock, so builds keep 2.20.0 and this edit is reverted on the next export.

Prompt for agents 
requirements-dev.txt is autogenerated by `uv export` (see its header) and is not consumed by CI; CI uses `uv sync --locked --extra dev` which reads uv.lock. This PR bumped pygments to 2.21.0 only in requirements-dev.txt, while uv.lock still pins pygments 2.20.0. As a result the upgrade does not take effect and the two lock representations diverge. Fix by updating pygments in uv.lock (both sdist and wheel entries with new version, hashes, and upload metadata) and regenerating requirements-dev.txt from the updated lock (`uv lock --upgrade-package pygments` then `uv export`), so both files agree and CI actually installs 2.21.0.
Open in Devin Review

Was this helpful? React with 👍 or 👎 to provide feedback.

# via pytest
pytest==9.1.1 \
--hash=sha256:1088fbde8f2b49d95a549a195707afa7a76a3ce9bcadc26b6d71f0ffda5fe313 \
Expand Down
Loading