fix(deps): update dependency websockets to v16

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
websockets (changelog)	>=15,<15.1 → >=16,<16.1

---

Release Notes

python-websockets/websockets (websockets)

v16.0

Compare Source

See https://websockets.readthedocs.io/en/stable/project/changelog.html for details.

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: uv.lock

Command failed: uv lock --upgrade-package websockets
Using CPython 3.13.12
  × No solution found when resolving dependencies for split (markers:
  │ python_full_version >= '3.14' and sys_platform == 'win32'):
  ╰─▶ Because google-genai>=1.30.0 depends on websockets>=13.0.0,<15.1.0 and
      only the following versions of google-genai are available:
          google-genai<=1.30.0
          google-genai==1.31.0
          google-genai==1.32.0
          google-genai==1.33.0
          google-genai==1.34.0
          google-genai==1.35.0
          google-genai==1.36.0
          google-genai==1.37.0
          google-genai==1.38.0
          google-genai==1.39.0
          google-genai==1.39.1
          google-genai==1.40.0
          google-genai==1.41.0
          google-genai==1.42.0
          google-genai==1.43.0
          google-genai==1.44.0
          google-genai==1.45.0
          google-genai==1.46.0
          google-genai==1.47.0
          google-genai==1.48.0
          google-genai==1.49.0
          google-genai==1.50.0
          google-genai==1.50.1
          google-genai==1.51.0
          google-genai==1.52.0
          google-genai==1.53.0
          google-genai==1.54.0
          google-genai==1.55.0
          google-genai==1.56.0
          google-genai==1.57.0
          google-genai==1.58.0
          google-genai==1.59.0
          google-genai==1.60.0
          google-genai==1.61.0
          google-genai==1.62.0
          google-genai==1.63.0
      we can conclude that google-genai>=1.30.0 depends on
      websockets>=13.0.0,<15.1.0.
      And because your project depends on google-genai>=1.30.0 and
      websockets>=16,<16.1, we can conclude that your project's requirements
      are unsatisfiable.

      hint: While the active Python version is 3.13, the resolution failed for
      other Python versions supported by your project. Consider limiting your
      project's supported Python versions using `requires-python`.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

• 🔍 Trigger a full review

---

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

[claude]

Pull Request Review: Update websockets to v16

Summary

This PR updates the websockets dependency from v15.x to v16.x. Overall, this is a straightforward dependency update that appears safe to merge.

---

✅ Positive Findings

1. Minimal Change: Only updates the version constraint in pyproject.toml - no code changes required
2. Existing Compatibility: The codebase already uses websockets.legacy.client (line 107 in app/services/upbit_websocket.py), which provides backwards compatibility for the legacy API
3. Well-Structured Code: The WebSocket implementation in app/services/upbit_websocket.py follows good practices:
   • Proper error handling with reconnection logic
   • SSL context configuration for macOS compatibility
   • Async context manager support
   • Clean separation of concerns

---

⚠️ Considerations & Recommendations

1. Test Coverage Gap

• Issue: No automated tests found for the WebSocket functionality
• Impact: Cannot verify that the upgrade doesn't break existing functionality
• Recommendation:

  # Before merging, manually test:
  python test_upbit_websocket.py
  # Or run the monitor:
  python upbit_websocket_monitor.py

2. Breaking Changes to Monitor

The websockets v16 release may include changes to the legacy client interface. Key areas to watch:

• Connection parameters (ping_interval, ping_timeout, close_timeout)
• SSL context handling
• Exception types and error handling

Recommendation: Review the websockets v16 changelog before merging.

3. CI/CD Coverage

• Good: Test workflow exists (.github/workflows/test.yml) with Redis service configured
• Gap: No integration tests for WebSocket connections
• Recommendation: Consider adding integration tests for WebSocket functionality in future PRs

4. Future Proofing

The code already uses websockets.legacy.client (line 107), which suggests awareness of API evolution. This is good practice and should continue.

---

🔒 Security Assessment

✅ No security concerns identified

• Dependency is from the official python-websockets project
• Version constraint >=16,<16.1 appropriately limits to minor versions
• SSL handling is already configured with proper context management

---

📊 Performance Considerations

✅ No performance concerns expected

• Version updates typically include performance improvements
• Existing connection pooling and reconnection logic remain unchanged

---

✅ Recommended Actions

Before Merging:

1. ✅ Manual Testing: Run python test_upbit_websocket.py to verify WebSocket connectivity
2. ✅ Review Changelog: Check websockets v16 release notes for breaking changes
3. ✅ Monitor CI: Ensure all CI checks pass

After Merging:

1. Monitor production logs for any WebSocket connection issues
2. Watch for SSL-related errors on macOS deployments

Future Improvements:

1. Add integration tests for WebSocket functionality
2. Consider adding health checks for WebSocket connections
3. Document version-specific requirements in UPBIT_WEBSOCKET_README.md

---

🎯 Conclusion

Verdict: ✅ APPROVE with manual testing recommendation

This is a clean dependency update that maintains backwards compatibility through the legacy client API. The risk is low, but manual testing is recommended before merging due to the lack of automated WebSocket tests.

The codebase demonstrates good engineering practices with proper error handling, reconnection logic, and documentation. The update aligns with keeping dependencies current while minimizing risk through constrained version ranges.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud