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.
| 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.
- Stabilizing the
v5API surface through point releases. - Documentation catch-up for v5 behavior changes (e.g. CORS /
RouteNotFoundbehavior on groups — see #2950). - Triaging and reducing the open issue / PR backlog.
These are frequently-requested items being discussed. Inclusion here is not a commitment — each still needs design agreement before implementation:
- Automatic
HEADforGETroutes (#2895; see #2949) — opt-in, likely via anOnAddRoutehook so users keep control. - Rate limiter response metadata — expose
Retry-After/ remaining quota through the store interface (#2961). - Real-IP /
Forwardedheader handling improvements (#2744). - Proxy middleware authorization-header handling (#2787).
- Continued alignment with the Go standard library (
net/http,slog). - Reducing third-party surface where the stdlib now covers the need.
- 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.