upgrade dependencies

[pan93412]

• chore: upgrade dependencies
• chore: update gqlgen resolvers

Summary by CodeRabbit

• Chores
  • Updated multiple dependencies to latest versions for improved security and stability.
  • Updated code generation tooling for enhanced code generation processes.
  • No functional changes to the application.

[coderabbitai]

Walkthrough

Routine dependency version updates across multiple Go modules in go.mod (gqlgen, Redis, testcontainers, CLI, oauth2, Google APIs, and golang.org packages). Code-generated resolver files automatically updated to reflect new gqlgen version 0.17.83 in their headers.

Changes

Cohort / File(s)	Summary
Dependency updates go.mod	Bumped versions for 18+ direct and indirect dependencies, including gqlgen (v0.17.81→v0.17.83), redis/rueidis (v1.0.67→v1.0.68), testcontainers-go (v0.39.0→v0.40.0), urfave/cli/v3 (v3.5.0→v3.6.0), oauth2, Google APIs, Docker, and golang.org packages (crypto, net, mod, sys, text, arch, sync).
Generated resolver header updates graph/database.resolvers.go, graph/ent.resolvers.go, graph/event.resolvers.go, graph/question.resolvers.go, graph/rank.resolvers.go, graph/user.resolvers.go	Code-generation header comment updated from gqlgen v0.17.81 to v0.17.83. No functional or logic changes; auto-generated metadata only.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

• Dependency versions: Verify that all version bumps are compatible and contain no breaking changes, particularly for gqlgen (code generator) and Go stdlib packages (crypto, net, sys).
• Generated files: Confirm that resolver auto-generation remains correct and no unexpected code changes occurred beyond the header update.

Poem

🐰 Dependencies dance, versions ascend,
gqlgen whispers of version 83,
Resolvers bow to the codegen trend,
golang.org modules stay in harmony,
Fresh bytes, fresh builds, old magic ends! ✨

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 'upgrade dependencies' is directly related to the main change, which involves updating go.mod with dependency version bumps and regenerating resolver files with the new gqlgen version.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

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

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 5e27963 and afe6a37.

⛔ Files ignored due to path filters (2)

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

📒 Files selected for processing (7)

• go.mod (6 hunks)
• graph/database.resolvers.go (1 hunks)
• graph/ent.resolvers.go (1 hunks)
• graph/event.resolvers.go (1 hunks)
• graph/question.resolvers.go (1 hunks)
• graph/rank.resolvers.go (1 hunks)
• graph/user.resolvers.go (1 hunks)

🔇 Additional comments (7)

graph/event.resolvers.go (1)

5-5: Generated header update confirmed. Auto-generated banner now reflects gqlgen v0.17.83, which aligns with the dependency upgrade; nothing else changed that needs attention.

graph/ent.resolvers.go (1)

5-5: Generated header update confirmed. Header string matches gqlgen v0.17.83 after the dependency bump; no additional changes present.

graph/database.resolvers.go (1)

5-5: Generated header update confirmed. Banner now references gqlgen v0.17.83, consistent with the upgraded go.mod; resolver logic remains untouched.

graph/question.resolvers.go (1)

5-5: Generated header update confirmed. Version string correctly tracks gqlgen v0.17.83 and there are no functional diffs to review.

graph/user.resolvers.go (1)

5-5: Generated header update confirmed. Auto-generated header aligns with gqlgen v0.17.83; rest of the resolver stays identical.

graph/rank.resolvers.go (1)

5-5: Header regeneration matches gqlgen v0.17.83.

Only the generator metadata changed, and no resolver logic was touched—looks good.

go.mod (1)

8-145: Dependency upgrades stay within safe version ranges.

All bumps are patch/minor releases on existing major versions, so compatibility risk is low and aligns with the regenerated gqlgen artifacts.

Warning

Review ran into problems

🔥 Problems

Git: Failed to clone repository. Please run the @coderabbitai full review command to re-trigger a full review. If the issue persists, set path_filters to include or exclude specific files.

---

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