🧹 chore: Update minimum go version to 1.24

[ReneWerner87]

Summary

• require Go 1.24 in docs and go.mod
• update CI workflows to use Go 1.24

Testing

• go test ./... (fails: proxyconnect tcp: dial tcp 172.26.0.3:8080: connect: no route to host)

[coderabbitai]

Walkthrough

The documentation for Fiber v3 has been updated to raise the minimum required Go version from 1.23 to 1.24. This update is reflected in the README, installation instructions, limitations, and the "What's New" documentation. Additionally, numerous benchmark test loops across various packages have been refactored to use the idiomatic b.Loop() method for iteration instead of traditional manual loop counters. No functional or API changes were introduced.

Changes

File(s)	Change Summary
.github/README.md, docs/intro.md, docs/whats_new.md	Updated documentation to require Go version 1.24 instead of 1.23 in installation instructions and notes.
app_test.go, bind_test.go, binder/_test.go, client/_test.go, ctx_test.go, helpers_test.go, internal/memory/memory_test.go, internal/storage/memory/memory_test.go, log/fiberlog_test.go, middleware/_test.go, path_test.go, redirect_test.go, redirect_test.go, router_test.go, services_test.go, state_test.go, log/default_test.go	Refactored all benchmark loops to use for b.Loop() instead of traditional for i := 0; i < b.N; i++ loops. Removed explicit calls to b.ResetTimer() and some b.StartTimer(). No logic changes.
listen.go	Changed printing of separator line in startup message from fmt.Fprintf with newline string to fmt.Fprintln.

Possibly related PRs

• chore: mark go1.23 as minimum go version #3226: Updates the minimum required Go version in documentation from 1.22 to 1.23, which is directly related as this PR continues by raising the requirement to 1.24.
• 🧹 chore: Update dependencies #3254: Adds a new benchmark function in router_test.go while this PR refactors existing benchmarks in the same file to use b.Loop().
• 📚 Doc: Update intro documentation #3204: Improves clarity and consistency of introductory documentation; related as both modify documentation though not overlapping in version requirements.

Suggested reviewers

• sixcolors
• efectn

Poem

🐇 Hopping through docs with a fresh new tune,
Go 1.24 now lights the moon.
Benchmarks loop with style anew,
Cleaner code, and tests that flew.
Fiber grows, it’s swift and bright,
Keep your Go updated right! ✨

---

📜 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 397e5c4 and c81045a.

📒 Files selected for processing (1)

• router_test.go (16 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• router_test.go

⏰ Context from checks skipped due to timeout of 90000ms (4)

• GitHub Check: unit (1.24.x, windows-latest)
• GitHub Check: unit (1.24.x, macos-13)
• GitHub Check: repeated
• GitHub Check: Compare

✨ Finishing Touches

• 📝 Generate Docstrings

---

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.
  • Explain this complex logic.
  • 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. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• 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 src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

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

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

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

Documentation and Community

• 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.

[Copilot]

Pull Request Overview

This PR updates the minimum Go version to 1.24 across documentation and CI configurations.

• Bumps the go directive in go.mod to 1.24
• Updates all references in docs and README from “1.23” to “1.24”
• Adjusts GitHub Actions workflows to only target Go 1.24.x

Reviewed Changes

Copilot reviewed 7 out of 7 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
go.mod	Updated Go version directive to 1.24.0
docs/whats_new.md	Adjusted dropped Go version requirement
docs/intro.md	Updated installation requirement text
.github/workflows/test.yml	Removed 1.23.x from test matrix and coverage filter
.github/workflows/linter.yml	Updated setup-go version to 1.24.x
.github/workflows/benchmark.yml	Updated setup-go version to 1.24.x
.github/README.md	Updated installation and compatibility notes

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 83.74%. Comparing base (d756ec1) to head (c81045a).
Report is 2 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3481      +/-   ##
==========================================
- Coverage   84.35%   83.74%   -0.61%     
==========================================
  Files         120      120              
  Lines       12190    12215      +25     
==========================================
- Hits        10283    10230      -53     
- Misses       1477     1561      +84     
+ Partials      430      424       -6     

Flag	Coverage Δ
unittests	83.74% <100.00%> (-0.61%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.