Skip to content
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

Update innovation release to MySQL 8.3.0. #1023

Closed
wants to merge 1 commit into from

Conversation

desrosj
Copy link

@desrosj desrosj commented Jan 18, 2024

Happy to make adjustments. I couldn't find good docs on the right steps to take when updating versions, but wanted to make a first pass.

@desrosj desrosj marked this pull request as ready for review January 18, 2024 15:06
@jnoordsij
Copy link
Contributor

Hey there! Thanks for your effort, I also noticed the new image has not appeared yet. These updates should be added automatically, but I noticed the automatic job triggering this is failing due to the new GPG key being used:

Packaging Notes
Important Change: The GnuPG build key (A8D3785C) used to sign MySQL downloadable packages has been updated. The previous GnuPG build key (3A79BD29) expired on 2023-12-14. For information about verifying the integrity and authenticity of MySQL downloadable packages using GnuPG signature checking, or to obtain a copy of our public GnuPG build key, see Signature Checking Using GnuPG.

Extracted from https://dev.mysql.com/doc/relnotes/mysql/8.3/en/news-8-3-0.html; similarly present on https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-36.html.

To ensure the image builds properly, an update of the Dockerfile templates containing updates to the GPG keys is needed. You should be able to add the new key and then run update.sh to ensure all templates and versions are properly updated.

If unsure how to proceed let me know, I'd be willing to follow-up with a new MR (or maybe a maintainer is ready to jump in? @tianon 😇).

@tianon
Copy link
Member

tianon commented Jan 18, 2024

Ouch, yep, thanks @jnoordsij! Looks like #1016 is back and now hitting the RPM repos (as noted by #1018 😂)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants