RTC PR-5.4-dev Pending

User tests: Successful: Unsuccessful:

avatar richard67
richard67
25 May 2026

Pull Request resolves # .

  • I read the Generative AI policy and my contribution is either not created with the help of AI or is compatible with the policy and GNU/GPL 2 or later.

Summary of Changes

This pull request (PR) updates the GitHub action "shogo82148/actions-setup-mysql" in our CI workflow from version v1.50.0 to version v1.51.0.

Changes see https://github.com/shogo82148/actions-setup-mysql/releases/tag/v1.51.0 .

Testing Instructions

Code review, and check that the integration tests in our CI workflow are successful for this PR.

Actual result BEFORE applying this Pull Request

GitHub action "shogo82148/actions-setup-mysql" is outdated.

Expected result AFTER applying this Pull Request

GitHub action "shogo82148/actions-setup-mysql" is up to date.

Link to documentations

Please select:

  • Documentation link for guide.joomla.org:

  • No documentation changes for guide.joomla.org needed

  • Pull Request link for manual.joomla.org:

  • No documentation changes for manual.joomla.org needed

avatar richard67 richard67 - open - 25 May 2026
avatar richard67 richard67 - change - 25 May 2026
Status New Pending
avatar joomla-cms-bot joomla-cms-bot - change - 25 May 2026
Category Repository
avatar richard67 richard67 - change - 25 May 2026
Title
[5.4] Update actions-setup-mysql GH action to v1.51.0
[5.4] Update actions-setup-mysql GitHub action to v1.51.0
avatar richard67 richard67 - edited - 25 May 2026
avatar richard67 richard67 - change - 27 May 2026
Status Pending Ready to Commit
Labels Added: PR-5.4-dev
avatar richard67
richard67 - comment - 27 May 2026

RTC after approval by 2 maintainers.


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/47827.

avatar richard67
richard67 - comment - 27 May 2026

RTC after approval by 2 maintainers.


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/47827.

avatar Hackwar
Hackwar - comment - 27 May 2026

Should we couple that to a specific release or simply always take the latest?

avatar richard67
richard67 - comment - 27 May 2026

Should we couple that to a specific release or simply always take the latest?

We should always couple it to a commit ID, see #47688 , and we should not update automatically but always review before. That's what I do with my recent couple of PRs for 5.4-dev, so after that all our actions will be up to date for now.

It could make sense to have an action or bot to cyclically check and notify maintainers or something like that, but there always should be a review before we update.

avatar muhme muhme - change - 27 May 2026
Labels Added: RTC
avatar muhme
muhme - comment - 27 May 2026

✅ Final check before merge

  • v1.51.0 is the latest shogo82148/actions-setup-mysql release
  • Verfified the full SHA
  • Checked CI passed
avatar muhme muhme - change - 27 May 2026
Status Ready to Commit Fixed in Code Base
Closed_Date 0000-00-00 00:00:00 2026-05-27 16:07:41
Closed_By muhme
avatar muhme muhme - close - 27 May 2026
avatar muhme muhme - merge - 27 May 2026
avatar muhme
muhme - comment - 27 May 2026

Thank you very much @richard67 for your contribution. Thank you @Hackwar for your support. Thanks to @laoneo and @tecpromotion for review.

Add a Comment

Login with GitHub to post a comment