Repository navigation
Please use new major version for Echo v5 support (semver) #142
Description
Activity
just a note: I plan to finish it this weekend
@akaroot and others. I retracted
v0.50.0inv0and createdv5for Echo 5.- Echo 5 use https://github.com/labstack/echo-contrib/releases/tag/v5.0.0
- Echo 4 use https://github.com/labstack/echo-contrib/releases/tag/v0.18.0
Echo 5 support
go get -u github.com/labstack/echo-contrib/v5
@aldas Thanks again for separating v5. However, for the v0 series, Go still lists v0.50.0 as the latest version on pkg.go.dev (see https://pkg.go.dev/github.com/labstack/echo-contrib?tab=versions
), even though v0.18.0 was released later.I created
v0.50.1that retractsv5things and is based onv4https://github.com/labstack/echo-contrib/releases/tag/v0.50.1
Hi, and thank you for maintaining this project.
The latest release v0.50.0 of echo-contrib appears to target Echo v5, while the previous release v0.17.4 is for Echo v4. Echo v5 is a new major version of the framework with significant breaking changes in the API and Context type.
To make the dependency relationship clearer and safer, would you consider aligning the major version of echo-contrib with the Echo major version it targets? For example:
This approach is already used by related Echo ecosystem projects (for example, echo-jwt uses v4.x.y for Echo v4 and v5.x.y for Echo v5). It would:
Clearly communicate which Echo major version a given echo-contrib release supports.
Prevent projects on Echo v4 from accidentally upgrading to an Echo v5-only echo-contrib release through loose constraints.
Make it easier for tools like Renovate and dependabot to manage upgrades across Echo major versions.
Even if you prefer to keep v0.x style versions, introducing a v5.x.y line for Echo v5 support (and documenting that v0.17.x is the latest Echo v4-compatible line) would greatly improve clarity for downstream users.
Thanks again for your work on Echo and echo-contrib.