-
-
Notifications
You must be signed in to change notification settings - Fork 800
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
Cannot go install github.com/air-verse/air@latest
#605
Comments
I just release a new version, should be fixed |
still have issue , so i revert the PR |
+1 seeing this as well |
I just revert the PR, still have issue? |
Yep, I'm still having the same error. |
just use the document one. at end of the day, i will update the document. |
Currently, I can't install |
will be github.com/air-verse/air in the end. |
For me, I had to replace |
This change broke all past versions of air as it's no longer possible to |
A proper fix for this will require some git history rewriting. The go module system is designed to be stable so changing the name like this will cause these expected integrity issues. You will need to rewrite references in all the commits so that all tags have the new e.g. should look like v1.52.2 https://github.com/air-verse/air/blob/v1.52.2/go.mod Should be doable with It might be better to leave v1 up at github.com/cosmtrek/air and make air-verse/air the v2 release with the original repo archived instead of redirecting. Either way the git history will need some love and the project overall will be in a messy state until this is resolved. |
FWIW My personal preference for how to handle this would be to archive and leave up the original repository with a note that it is deprecated and moved here. Start this one fresh with a commit that changes the names and then tag it as v2.0.0 to reflect the breaking change. You lose the old git history, but then the bifurcation is clean at least. If you want to keep the history, delete the old tags off of this repo. |
I got this error. Any update? |
It looks like a new tag hasn't been added yet so when go grabs latest it is the old version and it errors out.
Error message:
The text was updated successfully, but these errors were encountered: