build(deps-dev): Bump anyio from 4.14.1 to 4.14.2 in /services/account_unification

[dependabot]

Bumps anyio from 4.14.1 to 4.14.2.

Release notes

Sourced from anyio's releases.

4.14.2

• Changed ByteReceiveStream.receive() implementations to raise a ValueError when max_bytes is not a positive integer (#1191)
• Fixed CapacityLimiter.total_tokens rejecting float("inf") when the limiter was instantiated outside of an event loop. The adapter setter checked for infinity by identity (value is math.inf), so only the exact math.inf singleton was accepted, while every backend setter (using math.isinf()) accepts any positive infinity (#1189; PR by @​greymoth-jp).
• Fixed to_process.run_sync() deadlocking when the worker function writes enough data to sys.stderr to fill the (undrained) pipe buffer. The worker process now redirects sys.stderr to os.devnull as well, matching the documented behavior
• Fixed TLSStream.wrap() matching an internationalized (unicode) host name against the peer certificate using IDNA 2003 (via the standard library) instead of IDNA 2008, which could cause the host name to be matched against the wrong certificate (#1208)
• Fixed anyio.open_process() (and run_process()) ignoring the extra_groups argument, as it mistakenly passed the value of the group argument instead (#1209)
• Fixed CapacityLimiter.acquire_nowait() and CapacityLimiter.acquire_nowait_on_behalf_of() raising trio.WouldBlock instead of anyio.WouldBlock on the trio backend when there are no tokens available (#1218)
• Fixed CapacityLimiter on the asyncio backend over-granting tokens (borrowed_tokens exceeding total_tokens and available_tokens going negative) when a non-blocking acquire was made in the window between a token being released and the notified waiter resuming. The freed token is now reserved for the woken waiter right away, so the non-blocking acquire correctly raises WouldBlock (#1170; PR by @​gaoflow)
• Fixed unnecessary CPU spin when delivering cancellation from CancelScope on asyncio under certain conditions, including improper cancel scope nesting (#1111)

Commits

• c384f99 Bumped up the version
• dbba29d Fixed 100% CPU spin on cancel scope misuse (#1217)
• 6bbc6c3 Fix CapacityLimiter over-granting tokens on asyncio (#1172)
• 6f82b25 Refactored TestTLSStream.test_receive_invalid_max_bytes() to be less flaky
• be24b04 Relaxed timeouts to fix test flakiness
• 8113506 Fix test flakiness caused by slow callback duration logging
• 1e988b6 Fixed CapacityLimiter raising trio.WouldBlock instead of anyio.WouldBlock (#1...
• 44713f3 Pin setup-uv to a commit sha across downstream jobs (#1213)
• f1b7301 Fixed stderr writes in a worker subprocess causing a deadlock (#1207)
• 212be93 Fix flaky test_tcp_listener_same_port using a hardcoded port (#1206)
• Additional commits viewable in compare view

Summary by CodeRabbit

• Chores
  • 개발 환경에서 사용하는 anyio 의존성을 최신 버전으로 업데이트했습니다.
  • 업데이트된 버전에 맞게 무결성 검증 정보가 갱신되었습니다.

[opencode-agent]

Pull request overview

OpenCode could not approve from deterministic current-head evidence because GitHub Checks have failed.

Findings

1. HIGH Current-head GitHub Checks - Fix failed required checks before approval

• Problem: Failed same-head checks remain for 160f510029ceacc717671aaab996043fdfd20ad5.
• Root cause: The model-unavailable evidence fallback is allowed only when peer GitHub Checks are complete and clean.
• Fix: Read and fix the failed check logs below, then rerun the current-head checks.
• Regression test: Keep the model-unavailable fallback gated on an empty failed-check rollup.

Failed checks:

• SAST Semgrep/Semgrep (multi-language SAST): FAILURE (https://github.com/ContextualWisdomLab/keyverse/actions/runs/29406944642/job/87324589725)
• Semgrep (multi-language SAST) check run: failure (https://github.com/ContextualWisdomLab/keyverse/actions/runs/29406944642/job/87324589725)

Changed-File Evidence Map

flowchart LR
  PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
  Evidence --> S1["Changed file: requirements-dev.txt"]
  S1 --> I1["repository behavior"]
  I1 --> R1["Review risk: Changed file: requirements-dev.txt"]
  R1 --> V1["required checks"]

Loading

[opencode-agent]

OpenCode Review Overview

• Head SHA: 160f510029ceacc717671aaab996043fdfd20ad5
• Workflow run: 29406944373
• Workflow attempt: 1
• Gate result: REQUEST_CHANGES (approval step)

Pull request overview

OpenCode could not approve from deterministic current-head evidence because GitHub Checks have failed.

Findings

1. HIGH Current-head GitHub Checks - Fix failed required checks before approval

• Problem: Failed same-head checks remain for 160f510029ceacc717671aaab996043fdfd20ad5.
• Root cause: The model-unavailable evidence fallback is allowed only when peer GitHub Checks are complete and clean.
• Fix: Read and fix the failed check logs below, then rerun the current-head checks.
• Regression test: Keep the model-unavailable fallback gated on an empty failed-check rollup.

Failed checks:

• SAST Semgrep/Semgrep (multi-language SAST): FAILURE (https://github.com/ContextualWisdomLab/keyverse/actions/runs/29406944642/job/87324589725)
• Semgrep (multi-language SAST) check run: failure (https://github.com/ContextualWisdomLab/keyverse/actions/runs/29406944642/job/87324589725)

Changed-File Evidence Map

flowchart LR
  PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
  Evidence --> S1["Changed file: requirements-dev.txt"]
  S1 --> I1["repository behavior"]
  I1 --> R1["Review risk: Changed file: requirements-dev.txt"]
  R1 --> V1["required checks"]

Loading

[seonghobae]

@dependabot rebase

[coderabbitai]

📝 Walkthrough

Walkthrough

개발 환경의 anyio 버전을 4.14.2로 업데이트하고 해당 버전의 검증 해시를 갱신했습니다.

Changes

개발 의존성 업데이트

Layer / File(s)	Summary
anyio 버전 및 검증 해시 갱신 services/account_unification/requirements-dev.txt	anyio 버전을 4.14.1에서 4.14.2로 변경했습니다. 새 버전에 맞는 두 개의 검증 해시를 갱신했습니다.

Estimated code review effort: 1 (매우 낮음) | ~2분

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	제목은 /services/account_unification에서 anyio 개발 의존성을 4.14.1에서 4.14.2로 업데이트한 주요 변경 사항을 명확하게 설명합니다.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch dependabot/pip/services/account_unification/anyio-4.14.2

---

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@services/account_unification/requirements-dev.txt`:
- Around line 11-13: Update services/account_unification/uv.lock to regenerate
the anyio dependency entry at version 4.14.2, replacing the 4.14.1 metadata and
old distribution hashes with the hashes matching requirements-dev.txt. Keep the
lockfile consistent with the pinned anyio requirement.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 07a5dce4-c226-4ad8-b4e8-49d7315e0a3a

📥 Commits

Reviewing files that changed from the base of the PR and between 801ad87 and 5a68bf3.

📒 Files selected for processing (1)

• services/account_unification/requirements-dev.txt

[coderabbitai]

🗄️ Data Integrity & Integration | 🟠 Major | ⚡ Quick win

uv.lock도 anyio 4.14.2로 갱신해야 합니다.

services/account_unification/uv.lock는 아직 anyio 4.14.1과 이전 해시를 기록합니다. 두 파일의 잠금 정보가 불일치합니다. lockfile 기반 설치는 4.14.1을 유지하거나 잠금 검증에 실패할 수 있습니다. uv.lock를 재생성하고 4.14.2의 배포 파일 해시를 반영해 주세요.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@services/account_unification/requirements-dev.txt` around lines 11 - 13,
Update services/account_unification/uv.lock to regenerate the anyio dependency
entry at version 4.14.2, replacing the 4.14.1 metadata and old distribution
hashes with the hashes matching requirements-dev.txt. Keep the lockfile
consistent with the pinned anyio requirement.