-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Where did v9.5.4 go? #3057
Comments
https://pkg.go.dev/github.com/go-redis/redis/v9?tab=versions Only the prereleases are appearing under the v9 tag. Very strange. Edit: installing v9.5.2 appears to work |
This is an interesting test case for dependency management. The Forgejo release pipeline is currently broken because of that as well as the CI. I assume it was a mistake? Accidents happen. |
Hello, sorry for the inconvenience. There was a sync issue in regarding releases. We are planning to release a new version soon based on the betas that were released a few weeks ago and rolled 9.5.4 back within this repo. Regards, |
Thanks for the update ❤️ When will soon be?
Either way is fine. If it is going to happen within 24h, just waiting for it to happen is the best solution. If not reverting to a published version such as v9.5.2 is worth a little effort. |
Hi, I just wanted to update that we released v9.6 now. Again, sorry for the inconvenience that the release rollback caused. If OK with everyone here, I am going to close this issue. Regards, |
Thank you for the update @dmaier-redislabs . Line 5 in 3613df6
Looks like the v9.6 release got created from a tag/branch that has not been merged into master yet. And that version file seems to only be updated about half the time. |
How to solve this problem? my project does not build with any version from 9.5 to 9.6 with this error I tried clearing caches, changing goproxy, nothing helps. |
Where did v9.5.3 go? This breaks TykTechnologies/tyk#6424 build. |
well, after many tries this works for me
|
@MrSwed |
@martinsirbe As said, there was some confusion around the next upcoming release. Because of that, we rolled the unplanned releases (9.5.3 and 9.5.4) back and replaced them by a 9.6.0 release. Sorry for the the inconvenience. |
@marcind Because of the release rollback, we did speed the 9.6 release up, but we removed some of the features that are already in main (mainly search and query related stuff that we want to stabilize before releasing it to a new go-redis version). We are going to align and stabilize the main branch and will cut a new release with search and query within the next weeks. @vladvildanov @ofekshenawa Feel free to add additional details as needed. |
@dmaier-redislabs Thanks for taking a look at this issue! Go has official guidance on what to do in these cases that I think should be followed here. Since this release was out for some time, its code and sumdb entry are available in the official Go proxy, but not in this repository. This leads to two issues:
The correct approach here is to:
That solves both of these problems. You can see similar issues here:
where you can see how this would affect your users. Would you consider adding the git tags back and retracting the release on the |
Thank you @mx-psi for guiding us through this process! Again we sincerely apologise for the inconvenience we caused you. We just got released a new v9.6.1 that adds a retraction for v9.5.3 and v9.5.4 to follow the best practices in go community. |
Since this should be solved now, I am closing this issue. Please let us know if you should face any further issues. |
Thank you! .. extra are still old Click to expand
|
@MrSwed This seems to be unrelated to the accidental release of 9.5.3 and 9.5.4 because your example shows that it also happens with older versions. @ofekshenawa @vladvildanov Could you please open a new issue for this? |
v9.5.4 got released last Friday but today it is no longer listed under https://github.com/redis/go-redis/releases. However, I can still
go get github.com/redis/go-redis/[email protected]
. Did that release get unpublished? Is there an issue with it?The text was updated successfully, but these errors were encountered: