-
Notifications
You must be signed in to change notification settings - Fork 427
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
RabbitMQ 4.0.0 GA is here #726
Comments
We had a small race! 😂 |
The version is set to I now suspect it is an artifact of our (relatively) recent Makefile refactoring. It can take a few days to address. If this affects the builds of this image, we can disable the 4.0.x builds unless this is addressed. |
That doesn't affect the code that the server was built with, just the version string that is embedded in the binaries, right? If that is all, I think it is relatively harmless and will be fixed in a coming release. It will affect the value shown in SBOM scanner/generators (like those attached in the image index), but I don't think that'd change what future CVE's would apply to it. |
@yosifkit it only affects the version reported by the nodes (when the generic binary package is used) and the reported versions of plugins, including their directory names. Nothing else. It also does not affect many other artifact types so a package built from our source tarball with the correct inputs potentially won't exhibit this problem (the source tarball does not have any version information other than Git commits of all subprojects (what's under |
|
Excellent, will go out with docker-library/official-images#17604 👍 |
@yosifkit @tianon folks, RabbitMQ 4.0.0 has shipped (the website and plenty of other places will be updated/synced in the next few days).
Can we please graduate 4.0 to a GA series?
Thank you!
The text was updated successfully, but these errors were encountered: