chore: upgrade dependencies

[pan93412]

Summary by CodeRabbit

• Chores
  • Updated dependencies to their latest stable versions for enhanced system compatibility and improved application stability. These routine maintenance updates to core framework libraries and development tools ensure optimal performance, security, and reliability across modern environments. No user-facing changes.

[coderabbitai]

Walkthrough

Go module dependency versions are updated across 8 packages, including direct dependency github.com/urfave/cli/v3 and several indirect transitive dependencies related to QUIC, system configuration utilities, experimental Go libraries, and gRPC.

Changes

Cohort / File(s)	Change Summary
Dependency Version Updates go.mod	Updated 8 dependencies: urfave/cli/v3 (v3.6.0 → v3.6.1), quad-go/qpack (v0.5.1 → v0.6.0), quic-go/quic-go (v0.56.0 → v0.56.1-0.20251119080237-b7886d5c9017), tklauser/go-sysconf (v0.3.15 → v0.3.16), tklauser/numcpus (v0.10.0 → v0.11.0), golang.org/x/exp (v0.0.0-20251023... → v0.0.0-20251113...), golang.org/x/tools (v0.38.0 → v0.39.0), google.golang.org/grpc (v1.76.0 → v1.77.0).

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

• Verify that all updated dependencies are compatible with the current codebase
• Check release notes for any breaking changes, particularly in quic-go and grpc versions
• Confirm go.sum file is appropriately updated to match go.mod changes

Possibly related PRs

• upgrade dependencies #32: Also updates go.mod with overlapping dependency bumps including urfave/cli and quic-go.

Poem

🐰 With versions bumped and deps renewed,
Our module's channels are all smoothed,
From quic to grpc, they all align,
Fresh releases make the code just fine! ✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'chore: upgrade dependencies' clearly and concisely summarizes the main change—updating dependency versions in go.mod.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch upgrade-dependencies-1120

---

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

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

go.mod (1)

22-22: Other dependency updates look reasonable.

The remaining updates (urfave/cli v3.6.1, tklauser/go-sysconf v0.3.16, tklauser/numcpus v0.11.0, golang.org/x/exp, golang.org/x/tools v0.39.0, and google.golang.org/grpc v1.77.0) are patch or minor version updates with appropriate version increments. Consider running the test suite to ensure these updates don't introduce unexpected compatibility issues.

Also applies to: 115-115, 116-116, 137-137, 143-143, 145-145

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between cbd2144 and a2476c0.

⛔ Files ignored due to path filters (2)

• flake.lock is excluded by !**/*.lock
• go.sum is excluded by !**/*.sum

📒 Files selected for processing (1)

• go.mod (3 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)

• GitHub Check: Run Tests
• GitHub Check: Lint and Check Formatting

🔇 Additional comments (2)

go.mod (2)

109-109: Verify the pseudo-version dependency for quic-go/quic-go.

The update to github.com/quic-go/quic-go uses a pseudo-version (v0.56.1-0.20251119080237-b7886d5c9017) instead of a stable release tag. This indicates the code points to a specific development commit rather than a released version.

Please confirm whether this is intentional (e.g., to test pre-release functionality) or if a stable v0.56.1 release should be used instead.

---

108-108: Verify compatibility for the qpack minor version bump.

The update to github.com/quic-go/qpack crosses a minor version boundary (v0.5.1 → v0.6.0). In pre-1.0 versioning, minor version updates can introduce breaking changes. Please ensure that the rest of the codebase is compatible with the new qpack API.