User tests: Successful: Unsuccessful:
Pull Request resolves # .
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 .
Code review, and check that the integration tests in our CI workflow are successful for this PR.
GitHub action "shogo82148/actions-setup-mysql" is outdated.
GitHub action "shogo82148/actions-setup-mysql" is up to date.
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
| Status | New | ⇒ | Pending |
| Category | ⇒ | Repository |
| Title |
|
||||||
| Status | Pending | ⇒ | Ready to Commit |
| Labels |
Added:
PR-5.4-dev
|
||
RTC after approval by 2 maintainers.
Should we couple that to a specific release or simply always take the latest?
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.
| Labels |
Added:
RTC
|
||
✅ Final check before merge
| 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 |
Thank you very much @richard67 for your contribution. Thank you @Hackwar for your support. Thanks to @laoneo and @tecpromotion for review.
RTC after approval by 2 maintainers.
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/47827.