Echo V4 is not working anymore with the latest release

[lukasbash]

Within #140 the echo dependency just silently changed, causing all automated go upgrades to the latest version to fail with echo V4:

cannot use echoSwagger.EchoWrapHandler((func(c *echoSwagger.Config) literal)) (value of func type "github.com/labstack/echo/v5".HandlerFunc) as "github.com/labstack/echo/v4".HandlerFunc value in argument to e.GETcompiler[IncompatibleAssign](https://pkg.go.dev/golang.org/x/tools/internal/typesinternal#IncompatibleAssign)

Why is this breaking change not communicated and can you implement a backwards compatibility handler as for V3?

[ubogdan]

I see. How do you propose to get this solved now.

[lukasbash]

I see. How do you propose to get this solved now.

Not sure how you want to handle it, but usually one would create a /v2 package, yes?

[natewlew]

Similar issue here: labstack/echo-contrib#142

[akaroot]

I agree with @lukasbash. The best way to handle this is to release a new major version of echo-swagger that targets Echo v5, for example v2 (following semantic versioning) or v5 (to correspond with the Echo major version).

[lukasbash]

Any update @ubogdan ?

[ubogdan]

i hope is ok now.

[akaroot]

Unfortunately, it’s not OK because the Go packages still see version 1.5.0. https://pkg.go.dev/github.com/swaggo/echo-swagger?tab=versions
It looks like @ubogdan you need to bump the version to fix this issue.

[ubogdan]

bumped version to 1.5.1 in v1 repo. Deleted 1.5.0 release so it won't annoy users.

[pzduniak]

@ubogdan v1.5.1 still points at v2, v1.5.0 is still fed by the Go proxy

see https://github.com/swaggo/echo-swagger/blob/v1.5.1/go.mod and https://proxy.golang.org/github.com/swaggo/echo-swagger/@v/list

go: github.com/swaggo/echo-swagger@v1.5.1: invalid version: go.mod has post-v1 module path "github.com/swaggo/echo-swagger/v2" at revision v1.5.1```

[pzduniak]

@ubogdan I would happily contribute a fix to the project, but this is purely up to the maintainers to fix the repo. Can we please get a v1.5.2 pointing at the correct commit?