feat: support echo v5

[jinuthankachan]

closes #37

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	github.com/​labstack/​echo/​v5@​v5.1.0
	github.com/​getkin/​kin-openapi@​v0.135.0
	github.com/​stretchr/​testify@​v1.11.1

View full report

[mromaszewicz]

@jamietanna - what do you think, should we put echo V5 as a sub-module of echo-middleware or make a repo specifically for it?

The middleware itself, for V4 and V5 is basically identical.

I would love to see both just call through to shared code, but Go's module system makes it annoying since each sub-module requires its own git tag for each release to keep various tools happy, like Renovate.

[mromaszewicz]

Echo works fine with Go 1.25.0 (https://github.com/labstack/echo/blob/v5/go.mod), so I think we should try not to get ahead of it too much to allow as many users as possible to use this package. Lots of people can't update to the latest Go version immediately due to all kinds of internal company bureaucracy.

[jamietanna]

I think child Go module is ok but not like this right now - if we do, it'll cause Go module versioning confusion, and can make it seem like it's v5 of this module - I'd say maybe echov5

I agree that a separate repo may not be ideal given the shared code

Also, if we are doing a submodule, this will require we change our release process (which is fine, but calling it out)