1
0
mirror of https://github.com/labstack/echo.git synced 2026-06-13 21:54:53 +02:00
Files
echo/ROADMAP.md
Vishal Rana b0a391677a docs: liveness signals in README + public ROADMAP (#3002)
* docs: add liveness signals to README and a public ROADMAP

- Add dynamic latest-release and last-commit badges (can't go stale)
- Add positioning vs net/http and an "actively maintained" note
- Add ROADMAP.md with version policy (v5 current, v4 LTS to 2026-12-31)
  and surface it from the README

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

* docs: fix review findings in README/ROADMAP

- Correct net/http interop claim: Echo handlers are not http.Handler;
  interop is via WrapHandler/WrapMiddleware
- Clarify binding ships with a pluggable validator (not built-in validation)
- ROADMAP: reference canonical auto-HEAD issue/PR (#2895/#2949) instead of
  the duplicate PRs (#2944/#2937) slated for closure

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-13 12:06:48 -07:00

2.1 KiB

Echo Roadmap

DRAFT — this is a starting point for maintainers to edit, not a commitment. Dates and priorities are owned by the Echo team. Open a discussion to propose changes.

This document exists so the community can see where Echo is heading. Echo is actively maintained. We publish releases regularly across two supported lines — see README badges for the latest version and most recent commit.

Version policy

Line Status Support
v5 Current (since 2026-01-18) New features, fixes, and improvements.
v4 Maintenance / LTS Security and bug fixes until 2026-12-31. No new features.

Upgrading from v4? See API_CHANGES_V5.md.

Echo supports the latest four Go major releases and may work with older versions.

Now (in progress)

  • Stabilizing the v5 API surface through point releases.
  • Documentation catch-up for v5 behavior changes (e.g. CORS / RouteNotFound behavior on groups — see #2950).
  • Triaging and reducing the open issue / PR backlog.

Next (under consideration)

These are frequently-requested items being discussed. Inclusion here is not a commitment — each still needs design agreement before implementation:

  • Automatic HEAD for GET routes (#2895; see #2949) — opt-in, likely via an OnAddRoute hook so users keep control.
  • Rate limiter response metadata — expose Retry-After / remaining quota through the store interface (#2961).
  • Real-IP / Forwarded header handling improvements (#2744).
  • Proxy middleware authorization-header handling (#2787).

Later / exploratory

  • Continued alignment with the Go standard library (net/http, slog).
  • Reducing third-party surface where the stdlib now covers the need.

How to influence the roadmap

  • Discuss before large PRs — open a Discussion or issue so we can agree on the design first.
  • 👍 reactions on issues help us gauge demand.
  • See README → Contribute for contribution guidelines.