🐛 `fiber migrate --to v3` resolves to `3.0.0` instead of latest `3.x`

[MatiasRoje]

Issue description

I found an inconsistency between docs/user expectation and actual fiber migrate behavior.

The official docs mention this migration flow:
https://docs.gofiber.io/whats_new

As a user, when I run:

fiber migrate --to v3

I expect it to migrate to the latest stable 3.x release (best practice for security/patch updates), not to the first 3.0.0 release.

How to reproduce

go install github.com/gofiber/cli/fiber@latest
fiber migrate --to v3

• Output: Migration from Fiber 2.52.11 to 3.0.0
• go.mod is set to github.com/gofiber/fiber/v3 v3.0.0

When running without --to:

fiber migrate

it migrated to 3.1.0 (latest as of today), which is what I expected from major-target migration too.

Expected result

Either:

1. --to v3 resolves to the latest 3.x,
2. docs/help clearly state that major-only version input resolves to 3.0.0.

[welcome]

Thanks for opening your first issue here! 🎉 Be sure to follow the issue template! If you need help or want to chat with us, join us on Discord https://gofiber.io/discord

[coderabbitai]

🔗 Related PRs

#134 - Add full migration test from Fiber v2 to v3 [merged]
#135 - Add force & skip go mod options for migration [merged]
#163 - Allow forced v3 migration with existing v3 usage [merged]
gofiber/fiber#3708 - docs: add migration tool info [merged]
#272 - feat(migrator): add template version migration for Fiber v3 compatibility [merged]

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!