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

[dependabot]

⚠️ Dependabot is rebasing this PR ⚠️

Rebasing might not happen immediately, so don't worry if this takes some time.

Note: if you make any changes to this PR yourself, they will take precedence over the rebase.

---

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

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Summary by CodeRabbit

• 개선 사항
  • 개발 환경의 안정성과 호환성을 높이기 위한 내부 업데이트가 적용되었습니다.
  • 이번 변경으로 최종 사용자에게 제공되는 기능이나 화면에는 직접적인 변화가 없습니다.

[coderabbitai]

📝 Walkthrough

Walkthrough

개발 요구사항 파일에서 anyio를 4.14.2로 업데이트하고 해당 버전의 잠금 해시 두 개를 변경했습니다.

Changes

anyio 의존성 업데이트

Layer / File(s)	Summary
anyio 버전 및 해시 업데이트 services/account_unification/requirements-dev.txt	anyio 버전을 4.14.1에서 4.14.2로 변경했습니다. 새 버전에 맞게 두 개의 패키지 해시를 교체했습니다.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Possibly related PRs

• ContextualWisdomLab/keyverse#17: 같은 파일에서 anyio 버전과 해시를 동일하게 업데이트합니다.

Suggested reviewers: seonghobae

🚥 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 the dependency lock data for anyio to 4.14.2 in both
requirements.lock and uv.lock, regenerating them with the repository’s standard
lock-file tooling so all recorded hashes and metadata match the new version and
requirements-dev.txt.

🪄 Autofix

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: 2bee71c8-469e-4240-b8f5-a788be433327

📥 Commits

Reviewing files that changed from the base of the PR and between 8743ae5 and a958269.

📒 Files selected for processing (1)

• services/account_unification/requirements-dev.txt

[coderabbitai]

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

관련 잠금 파일을 함께 갱신하세요.

services/account_unification/requirements-dev.txt는 anyio==4.14.2를 지정하지만, services/account_unification/requirements.lock과 services/account_unification/uv.lock은 여전히 4.14.1과 이전 해시를 사용합니다. 해당 잠금 파일을 사용하는 설치 경로는 계속 4.14.1을 설치합니다. 저장소의 잠금 파일 생성 도구로 두 파일을 재생성하고 새 버전과 해시가 일치하는지 확인하세요.

🤖 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 the dependency lock data for anyio to 4.14.2 in both requirements.lock
and uv.lock, regenerating them with the repository’s standard lock-file tooling
so all recorded hashes and metadata match the new version and
requirements-dev.txt.

[seonghobae]

Superseded by merged PR #66 (65537548d70df2a29752f7f7b57728febc7d030f). The AnyIO update is included in one current-main, lock-consistent dependency graph whose pyproject.toml, uv.lock, runtime export, and development export passed the complete repository gates.

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.