-
Notifications
You must be signed in to change notification settings - Fork 203
Invalid Iris dependency #70
Comments
I just tried to run the same command on my machine and it worked. I have attempted to clean the ~/go/pkg/mod cache and every time I see the |
@sapessi The maintainer of iris said that he deleted all of legacy tags: kataras/iris#1571 |
Iris users were not the only ones left behind by using legacy package import (github.com/kataras/iris instead of github.com/kataras/irisv12). The users of echo web framework, was left behind too. Echo's latest version is So, I am preparing a PR which will update all dependencies, including Iris and Echo. |
…ll continue use this package relative to: awslabs#70
OK It's done, it was a simple task. Please vote up or comment your opinion at: #71. Thanks, |
I'm working on the iris update now. Echo is a bigger breaking change. I think we should just switch to #65 and simply support the http adapter. We can then give samples that show how to use it with each framework. |
See #72 - I may merge and tag as a major release |
Closing since we merged #71 |
Since today I'm unable to build my go application using
aws-lambda-go-api-proxy
due to an invalid version of theiris
dependency.And after looking into the
github.com/kataras/iris
, there is nov11.1.1
version. At this point, I'm not sure how did it work before - did thegb.xjqchip.workers.dev/kataras/[email protected]
got deleted from their github, or am I missing something?The text was updated successfully, but these errors were encountered: