mysql:5.7 image changing Linux Distribution (breaking change?)

[OsamaNabih]

We've been using mysql:5.7 image in our company for months now.
Suddenly today all our builds started failing.
After checking mysql's dockerhub, it came to our attention there had been a new push to the image.
After some debugging, we found out that the image mysql:5.7 now uses Oracle Linux.
As far as we know, this image had always used buster-slim.
Is it mentioned anywhere that the generic images use Oracle by default, or was this a mistake?
Please let us know so we can best consider our options.
@tianon Followup would be appreciated. Thank you for all your work.

You can see in the image the default and the oracle tag images are using the same digest.

[magnusbarata]

Please see this issue.
In short, try to use mysql:5.7-debian.
They did intentionally change the default image to "oracle" variants, although haven't document it anywhere AFAIK.

[wglambert]

The change was from #867
We don't have a great way of communicating changes to users outside of pull requests and commits in these repos, so to be aware of upcoming and past changes check out the PR's over at https://github.com/docker-library/official-images/issues?q=label%3Alibrary%2Fmysql+is%3Aclosed

A good practice to use is a more specific tag that specifies the OS, and major.minor release numbers which are under "supported tags" https://hub.docker.com/_/mysql/

[OsamaNabih]

We have indeed shifted to using the more specific "-debian" images.
Thank you.

[ap-wtioit]

Just as an additional warning to everybody:

The openssl included in mysql:5.7 got downgraded from OpenSSL 1.1.1n 15 Mar 2022 to OpenSSL 1.0.2k-fips 26 Jan 2017
https://www.cvedetails.com/vulnerability-list/vendor_id-217/product_id-383/version_id-577438/Openssl-Openssl-1.0.2k.html