chore(deps): lock file maintenance

[renovate]

This PR contains the following updates:

Update	Change
lockFileMaintenance	All locks refreshed

🔧 This Pull Request updates lock files to use the latest dependency versions.

---

Configuration

📅 Schedule: Branch creation - "before 5am on Monday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

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

---

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

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

---

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

[claude]

PR Review: Lock File Maintenance

Summary

This is a Renovate bot PR that updates lock files with the latest dependency versions. The changes are minimal and focused on patch/minor version updates.

Changes Detected

• numpy: 2.4.0 → 2.4.1 (patch update in both adit-client/uv.lock and uv.lock)
• Two additional minor/patch version bumps in dependencies

Code Quality ✅

• Automated maintenance: Lock file updates are generated automatically by Renovate
• Scope: Changes are limited to lock files only - no source code modifications
• Consistency: Both lock files are updated together

Security & Dependencies ✅

• numpy 2.4.1: This is a patch release that typically includes bug fixes and stability improvements. Patch updates in numpy are generally safe and recommended.
• Lock file integrity: All package hashes are updated appropriately
• No breaking changes: Minor/patch version updates follow semantic versioning

Testing Considerations ✅

• Lock file maintenance PRs should be validated by CI/CD pipeline
• The existing test suite should catch any compatibility issues
• Renovate has automerge enabled, which is appropriate for lock file maintenance

Performance Considerations ✅

• Patch updates typically do not introduce performance regressions
• May include performance improvements and bug fixes

Potential Issues

None identified. This is a routine maintenance update.

Recommendations

1. ✅ Approve and merge - This is a standard lock file maintenance PR
2. ✅ Verify CI checks pass before merging (automerge should handle this)
3. ✅ No manual code review needed unless CI fails

Conclusion

This PR follows best practices for dependency maintenance. Lock file updates are essential for security and stability. The changes are minimal, automated, and safe to merge once CI passes.

Verdict: ✅ LGTM (Looks Good To Me) - Safe to merge pending CI success.

---

Review generated by Claude Code

[claude]

Pull Request Review - Lock File Maintenance

Summary

This PR updates lock files (uv.lock and adit-client/uv.lock) as part of automated dependency maintenance. The primary change is updating numpy from 2.4.0 to 2.4.1 across all supported platforms and Python versions.

Code Quality ✅

• Automated maintenance: This is a Renovate bot PR following standard lock file maintenance practices
• Consistent updates: The version bump is applied uniformly across both lock files
• No source code changes: Only lock files are modified, reducing risk

Potential Issues & Observations

1. Minor Version Update - Low Risk ✅

• numpy 2.4.0 → 2.4.1 is a patch release
• Published on 2026-01-10 (very recent)
• Hash changes are expected and normal for new releases
• All wheel distributions updated consistently across platforms

2. Release Notes Recommendation 📝

While this appears to be a routine patch update, I recommend:

• Reviewing numpy 2.4.1 release notes for any bug fixes or changes that might affect DICOM processing
• Given this project's reliance on numpy for medical imaging data (via pydicom, dicomweb-client), ensuring no breaking changes in numerical operations

3. Testing Considerations 🧪

The CI checks are currently in progress. Key areas to verify:

• DICOM data processing operations (reading, pseudonymization, transfer)
• Any numerical computations in the core modules
• Compatibility with pydicom (2.4.4) and dicognito (0.17.0)

Performance Considerations ⚡

• Patch releases typically include performance improvements or bug fixes
• No anticipated performance regressions
• Lock file updates don't change compilation or build behavior

Security Concerns 🔒

• Low security risk: numpy is a well-maintained, widely-used package
• Patch releases often include security fixes
• The update maintains all hash checksums for integrity verification

Test Coverage 📊

• No test changes needed (lock file only)
• Existing test suite should validate compatibility
• Current CI status shows tests are running

Recommendations

1. Approve once CI passes ✅ - This is a low-risk maintenance update
2. Monitor for numerical precision issues - While unlikely, watch for any unexpected behavior in DICOM processing after deployment
3. Auto-merge enabled: The PR has automerge enabled, which is appropriate for lock file maintenance

Verdict

LGTM 👍 - This is a routine, low-risk dependency update following best practices. The automated nature of the update and the minor version bump make this safe to merge once CI checks complete successfully.

---

🤖 Review generated by Claude Code