Skip to content

build(deps-dev): bump httpcore2 from 2.9.1 to 2.12.0 in /services/account_unification #122

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 httpcore2 from 2.9.1 to 2.12.0 in /services/account_unification #122

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 @@ -300,9 +300,9 @@ httpcore==1.0.9 \
--hash=sha256:2d400746a40668fc9dec9810239072b40b4484b640a8c38fd654a024c7a1bf55 \
--hash=sha256:6e34463af53fd2ab5d807f399a9b45ea31c3dfa2276f15a2c3f00afff6e176e8
# via httpx
httpcore2==2.9.1 \
--hash=sha256:4d8acbf8b306f48c9d6046591fd5ba4037d1b1b1000d140fc2c3eab1e9a0c0e2 \
--hash=sha256:6182472379e855fe4221246a2bb7ecede403bc61c6798062ae1787d051ccde26
httpcore2==2.12.0 \
--hash=sha256:7e04258ce01013d7d615e5b910a3b27fac937d7a95038227e79652b4ba3b4ceb \
--hash=sha256:9293522bba0aa7c4c8e9e3f040c16575bd8868e155a77fa30c7a9085a5eae648
Comment on lines +303 to +305

@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.

🔴 Dev requirements pin diverges from the lockfile

httpcore2 is bumped to 2.12.0 in the generated dev requirements, but uv.lock still resolves 2.9.1 and httpx2 stays at 2.9.1 in both the requirements file and pyproject.toml. The four dependency surfaces are meant to come from one resolver run (doctoring record); editing only this one makes them disagree, so uv lock --check fails and uv sync --locked still installs 2.9.1.

Prompt for agents 
The bump of httpcore2 to 2.12.0 was applied only to the generated services/account_unification/requirements-dev.txt. The other dependency surfaces are inconsistent: services/account_unification/uv.lock still pins httpcore2==2.9.1 (see the [[package]] entry for httpcore2), and httpx2 remains ==2.9.1 in both requirements-dev.txt and pyproject.toml. docs/doctoring/2026-08-dependency-and-packaging-refresh.md states pyproject.toml, uv.lock, requirements.lock, and requirements-dev.txt are regenerated from one resolver execution and must not be edited independently, and CI runs `uv lock --check` and `uv sync --locked --extra dev`. Regenerate all dependency surfaces from a single uv resolver run so uv.lock (and any httpx2 constraint) is consistent with requirements-dev.txt, rather than hand-editing the generated dev requirements file.
Open in Devin Review

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

# via httpx2
httpx==0.28.1 \
--hash=sha256:75e98c5f16b0f35b567856f597f06ff2270a374470a5c2392242528e3e3e42fc \
Expand Down
Loading