New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(deps): cleanup go.mod file #1217
Conversation
Codecov Report
@@ Coverage Diff @@
## master #1217 +/- ##
=======================================
Coverage 83.65% 83.65%
=======================================
Files 58 58
Lines 3285 3285
=======================================
Hits 2748 2748
Misses 456 456
Partials 81 81 Continue to review full report at Codecov.
|
so, downgrade the cors lib? |
To my memory, that was the issue when doing Also, I think it is indrect dependency of |
oh yah, you're right. thanks! 🚀 |
@chenrui333 check #1218 |
Interesting, I did not have the same error in my local though. |
I switched back to go1.13, and the issue does pop up. I will submit a dependabot issue on this matter. |
@caarlos0 Just reported an issue. |
Thanks @chenrui333 ! :) |
It's still the same problem that I fixed in #1138 It's not an issue with dependabot, as it's the expected behavior. The problem need to be fixed in gitea. |
IMHO if it works on go1.13 only, its fine. we just need to change the docs https://github.com/goreleaser/goreleaser/blob/master/CONTRIBUTING.md
|
The The So, for me this PR must be reverted. |
I am little bit confused on why need to support both go 1.12 and go 1.13? This is more like a developer-oriented tool and we should constantly keep it using the latest go offering. |
does not seem to be, hence the build passing on go 1.13 🤔 |
I think the build passed, right? The dependabot PR build issue is indeed concerning, but I think that sounds like they need to do the environment update on their end, still waiting for their response on this though. |
The And |
The CI need to validate the A quick way to validate that:
|
CI does that already:
|
@ldez I believe it passed CI, it is just the dependabot environment needs to be updated to use latest golang. I works on go v1.13.3 but not v1.13 though. |
I use go1.13.3 and I need to set the $ go version
go version go1.13.3 linux/amd64
$ go mod tidy
go: code.gitea.io/gitea@v1.10.0-dev.0.20190711052757-a0820e09fbf7 requires
github.com/go-macaron/cors@v0.0.0-20190309005821-6fd6a9bfe14e9: invalid pseudo-version: revision is longer than canonical (6fd6a9bfe14e) $ go mod download
go: finding github.com/go-macaron/cors v0.0.0-20190309005821-6fd6a9bfe14e9
go: finding github.com/go-macaron/cors v0.0.0-20190309005821-6fd6a9bfe14e9
github.com/go-macaron/cors@v0.0.0-20190309005821-6fd6a9bfe14e9: invalid pseudo-version: revision is longer than canonical (6fd6a9bfe14e) |
let me re-check. :) |
@caarlos0 I find the tricks:
I think that |
Good finding. Isn't the default goproxy goes to |
It's a fallback system: https://proxy.golang.org > https://gocenter.io > direct |
That is right That is what is in Makefile though: |
I confirm: the problem come from https://gocenter.io https://proxy.golang.org/github.com/go-macaron/cors/@v/v0.0.0-20190309005821-6fd6a9bfe14e9.info
|
cc/ @ankushchadha |
Version
Google's proxy seems to have an opinion about the pseudoversion format which is compatible with Go 1.13, that is why it is returning an error when you try to fetch it from there.
The fix should be move away from this version and use the latest |
The problem comes because the date
This PR do the inverse: use |
Sorry, my mistake. We should move to the latest version of the dependency or fix the pseudoversion to be right one for that commit hash:
They apparently fixed it on |
I fixed the problem. |
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
No description provided.