chore: bump ezutil to v2

[itsLeonB]

Summary by CodeRabbit

• Chores

  • Upgraded a core utility library to v2 for improved compatibility and maintenance.
  • Pruned unused indirect dependencies to reduce footprint and simplify builds.

• Refactor

  • Updated internal imports to align with the new dependency version; no behavior changes.

• Tests

  • Adjusted tests to reflect dependency updates; no changes to test coverage or scenarios.

No user-facing features or behavioral changes are introduced in this release.

[coderabbitai]

Walkthrough

Updated ezutil dependency to v2 across code and tests. Adjusted go.mod to require github.com/itsLeonB/ezutil/v2 v2.0.0-alpha, removed several indirect dependencies, and added github.com/kr/text indirectly. No code logic or exported API changes in the touched files.

Changes

Cohort / File(s)	Summary
ezutil v2 import update error_middleware.go, http_server.go, middlewares.go, utils.go, test/http_server_test.go	Updated imports from github.com/itsLeonB/ezutil to github.com/itsLeonB/ezutil/v2; code references remain the same (e.g., ezutil.Logger, ezutil.Parse[T]).
Module dependencies go.mod	Switched dependency to github.com/itsLeonB/ezutil/v2 v2.0.0-alpha; removed various indirect deps (e.g., pg, gorm, jwt, mysql) and added indirect github.com/kr/text v0.2.0.

Sequence Diagram(s)

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

I nudge my deps with a whiskered grin,
Hop to v2, let imports begin.
Go mod trimmed like a hedge in spring,
Fewer twigs, same sturdy swing.
Thump-thump! The build still sings—
A tidy warren for future things. 🐇✨

✨ Finishing Touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch dev

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

go.mod (1)

3-3: Nit: use go 1.25 instead of go 1.25.0.

The go directive is major.minor; dropping the patch avoids tool warnings and is the convention.

Apply:

-go 1.25.0
+go 1.25

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 58eb903 and 24f5a93.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (6)

• error_middleware.go (1 hunks)
• go.mod (2 hunks)
• http_server.go (1 hunks)
• middlewares.go (1 hunks)
• test/http_server_test.go (1 hunks)
• utils.go (1 hunks)

🔇 Additional comments (8)

error_middleware.go (1)

13-13: LGTM: import bumped to ezutil/v2 with no behavioral change.

Interface use (ezutil.Logger) remains consistent; no further action needed here.

utils.go (1)

6-6: LGTM: switched to ezutil/v2; Parse[T] usage unaffected.

No observable logic change; safe bump.

test/http_server_test.go (1)

8-8: LGTM: test imports updated to ezutil/v2.

MockLogger continues to satisfy ezutil.Logger; compile-time checks will guard interface drift.

http_server.go (2)

12-12: LGTM: ezutil import migrated to v2.

Public API usage unchanged; looks consistent with the repo-wide migration.

---

12-12: v2 Migration Verified – No Further Action Required

All checks passed confirming the v2 migration is complete:

• No stray v1 imports found across the repository.
• go.mod correctly requires github.com/itsLeonB/ezutil/v2 v2.0.0-alpha.
• No leftover v1 entries in go.sum.
• All relevant files now import the v2 module.

Great work on the migration!

middlewares.go (1)

9-9: LGTM: import path updated to ezutil/v2.

Consistent with other files; no functional impact.

go.mod (2)

28-28: OK: new indirect github.com/kr/text v0.2.0.

Benign indirect (commonly pulled by difflib/testify). No action needed.

---

9-9: Major-version bump to v2 confirmed

• No lingering github.com/itsLeonB/ezutil (v1) imports detected
• All imports updated to github.com/itsLeonB/ezutil/v2
• go mod tidy && go mod download && go mod verify completed cleanly
• CI can fetch the v2.0.0-alpha tag successfully

No further action required.