Repository navigation
build(deps-dev): bump httpcore2 from 2.9.1 to 2.12.0 in /services/account_unification - #122
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [httpcore2](https://github.com/pydantic/httpx2) from 2.9.1 to 2.12.0. - [Release notes](https://github.com/pydantic/httpx2/releases) - [Commits](pydantic/httpx2@v2.9.1...v2.12.0) --- updated-dependencies: - dependency-name: httpcore2 dependency-version: 2.12.0 dependency-type: direct:development update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
| httpcore2==2.12.0 \ | ||
| --hash=sha256:7e04258ce01013d7d615e5b910a3b27fac937d7a95038227e79652b4ba3b4ceb \ | ||
| --hash=sha256:9293522bba0aa7c4c8e9e3f040c16575bd8868e155a77fa30c7a9085a5eae648 |
There was a problem hiding this comment.
🔴 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.
Was this helpful? React with 👍 or 👎 to provide feedback.
|
Exact-head admission audit: 현재 blocker:
유효 commit·diff·review evidence를 보존한 채 Draft/Proposed로 교정합니다. Base 이동이나 queue 대기만으로 Close하지 않으며 Force Push·synthetic status/approval·manual rerun·bypass를 사용하지 않습니다. Blocker 수리 후 새 exact head에서 Checks와 review admission을 다시 받아야 합니다. |
Bumps httpcore2 from 2.9.1 to 2.12.0.
Release notes
Sourced from httpcore2's releases.
... (truncated)
Commits
71ae23bVersion 2.12.0 (#1147)4fd0c70Decode compressed response bodies incrementally (#1126)d588e52Usebackports.zstdon Python 3.13 and earlier (#1146)344589dVersion 2.11.0 (#1143)de96d81Validate multipart part headers (#1142)51c3269Require brotli 1.2.0 in the brotli extra (#1141)829b93aRespect explicit Transfer-Encoding headers (#1137)4fa6c8eFix changelog extraction regex for H2 release headings (#1136)8a6f370Restore deprecated status code aliases (#1135)6f38ddfCache sniffio availability instead of importing it on every call (#1132)You can trigger a rebase of this PR by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)