V3 Beta Feedback: Help Us Fix Issues Before RC Release

[sixcolors]

V3 Beta Feedback: What Needs Fixing Before RC?

Hi Fiber community,

We're gearing up to ship V3's release candidate (RC) by mid-July 2025, but we need your help to make sure it’s rock-solid. V3’s been in beta too long, and we suspect some bugs or usability issues are holding us back. This issue is a poll to figure out what’s broken or not working right in the V3 beta (v3.0.0-beta.4).

Please share specific issues you’ve hit—bugs, performance problems, confusing APIs, or anything else. Use this template:

Issue Description:
Title / Link to Github Issue

• What’s broken or not right?
• Steps to reproduce (code snippets help!)
• Expected vs. actual behavior
• Environment (Go version, OS, etc.)

Our Plan to Ship V3

We’ve let too many niche features delay V3, so we’re locking it down to focus on stability. Here’s what we’re doing and why:

• Feature Freeze: No new features, just bug fixes and core improvements to ensure a stable RC.
• Timeline: RC by mid-July 2025, stable release by mid-August 2025, to get V3 into production ASAP.
• Community Feedback: A poll will help us prioritize fixes based on what you’re seeing in the wild.
• Stricter PRs: All pull requests must have documentation including migration guide in whats_new.md, and solid tests to avoid new issues.
• Docs Update: We’re refreshing whats_new.md and other docs to reflect changes and make V3 easier to adopt.

Poll: Comment with a 👍 on the issues below that you think are critical to fix before RC. Or add your own.

We’ll review your feedback by May 30, 2025, prioritize the top issues, and share a fix plan. Thanks for helping us make V3 awesome!

[sixcolors]

Make fiber.Ctx implement context.Context #3344

• What’s broken or not right?: Having too many different types of contexts is confusing - especially for new people transitioning from other languages to Go. If it's going to be simplified, now is the time to do it.
• Steps to reproduce: If the user wants to pass custom values around from middleware to middleware etc, they can directly store it in fasthttp's request's user values OR even better, we make fiber.Ctx implement context.Context and allow them to store it in there.
• Expected vs. actual behavior: N/A
• Environment (Go version, OS, etc.): N/A

[sixcolors]

Allow removing registered route #3098

• What’s broken or not right?: Following the addition of RebuildTree method 🚀 [Feature]: Allow rebuilding route tree stack #2769, which enabled dynamic request handling, @rebaz94 proposed enhancing this functionality by allowing the removal of registered routes.
• Steps to reproduce: N/A
• Expected vs. actual behavior: N/A
• Environment (Go version, OS, etc.): N/A