fix(deps): update module golang.org/x/sys to v0.38.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
golang.org/x/sys	v0.37.0 -> v0.38.0

---

Configuration

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

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 86.88%. Comparing base (c3c9c71) to head (5669288).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #584   +/-   ##
=======================================
  Coverage   86.88%   86.88%           
=======================================
  Files          12       12           
  Lines        1761     1761           
=======================================
  Hits         1530     1530           
  Misses        155      155           
  Partials       76       76           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[claude]

PR Review: Update golang.org/x/sys to v0.38.0

Summary

This is an automated dependency update from Renovate that bumps golang.org/x/sys from v0.37.0 to v0.38.0.

Code Quality ✅

• Clean dependency update: The changes are minimal and focused on updating the dependency version in go.mod and go.sum
• Follows project conventions: Automated dependency management is a good practice
• Proper semantic versioning: Minor version bump (v0.37.0 → v0.38.0) suggests backward compatibility

Impact Analysis ✅

The golang.org/x/sys package is used in this codebase for low-level socket operations:

Files affected:

• control_unix.go:10 - Uses golang.org/x/sys/unix for SO_REUSEADDR and SO_REUSEPORT socket options
• control_windows.go:6 - Uses golang.org/x/sys/windows for Windows socket options

Usage details:

• Unix platforms: unix.SetsockoptInt() for socket reuse configuration
• Windows: windows.SetsockoptInt() for SO_REUSEADDR

These are stable, well-established APIs that rarely change in breaking ways between minor versions.

Potential Issues 🟡

Low Risk Areas:

1. API Stability: The socket option APIs (SetsockoptInt, SO_REUSEADDR, SO_REUSEPORT) are core POSIX/Windows APIs unlikely to change
2. Platform Coverage: The codebase supports multiple Unix variants (Linux, FreeBSD, Darwin, AIX, DragonFly, NetBSD, OpenBSD) - ensure CI tests across these platforms

Recommendation: Verify CI passes on all supported platforms before merging.

Performance Considerations ✅

• Minor version updates of golang.org/x/sys typically don't introduce performance regressions
• No performance concerns identified

Security Considerations ✅

• Keeping dependencies up-to-date is a security best practice
• golang.org/x/sys is maintained by the Go team and receives regular security updates
• No known security issues with the update

Test Coverage ✅

Existing tests should cover the affected code:

• The project has comprehensive test files including transfer_test.go, transfer_active_test.go, and no_ports_test.go
• Socket operations are tested indirectly through FTP transfer tests
• CI should run with -race flag per CLAUDE.md conventions

Verification checklist:

• CI passes (including race detection)
• Tests pass on all supported Unix platforms
• Tests pass on Windows
• No new golangci-lint warnings

Recommendations ✅

1. Auto-merge is appropriate - This is a safe dependency update with automerge enabled
2. Monitor CI - Ensure all platform tests pass before merge
3. Future consideration - Consider adding explicit integration tests for socket reuse behavior if not already present

Conclusion

LGTM with CI verification - This is a routine, low-risk dependency update that maintains good security hygiene. The changes are minimal and affect well-tested, stable APIs. Once CI passes on all platforms, this is safe to merge.