-
Notifications
You must be signed in to change notification settings - Fork 51
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
Install issue between version 2.7.0
and v2.7.3
#335
Comments
That seems to be the breaking change 😕 |
and the upgrade from |
I think the best would be to delete |
another issue is that v3 isn't available on pkg.go.dev |
Hey @viceice how does a package get published on pkg.go.dev? I think I've never submitted it there. |
i think they get automatically grabbed when properly defined. your v3 releases can't be installed via Line 1 in 2d43756
this version always need to correspond with your major version github tags / releases |
also your version 2.8.0 isn't visible because of the missing |
so you should publish a new |
It's a common misconception, but go package versions can not really be deleted because go proxies already have them in cache and that cache is immutable. Just publish a fixed patch release instead. Deleting a git tag would only break it more because then people behind a go proxy that does not have the cache entry will get a broken install. Just never delete tags on a go package repo please. |
Indeed, but they can be retracted: https://go.dev/doc/modules/gomod-ref#retract |
I think this issue can be closed now, since #338 is merged. |
We're trying to automatically upgrade this package1
so we used
go install github.com/editorconfig-checker/editorconfig-checker/cmd/[email protected]
before which works.since
v2.7.3
we need to switch togo install github.com/editorconfig-checker/editorconfig-checker/v2/cmd/[email protected]
.What's the reason to add the
v2
after the name? it seems to be a breaking change for the v2 module.Footnotes
https://codeberg.org/forgejo/forgejo/pulls/3178 ↩
The text was updated successfully, but these errors were encountered: