That would have caught that blocker: bug 40292 So it's about forking Koha_Main_MariaDB_update and switching the DBMS. It should be ok to leave it on main to be sure to not miss DB revs to test. The trade off is the risk of dropping that new MDB 10.3 upgrade job when that version is dropped from main. That's a more general issue of CI going out of sync with: https://wiki.koha-community.org/wiki/System_requirements_and_recommendations To not risk any of the two trade offs above, we would need to have that job on main, 24.11 LTS and 25.05 (as some db rev would be only on 25.05). That would be a waste of resources.
Is there a large enough risk for needing also mariadb latest ? I though I had found a case but it was about something in kohastructure.sql (offset became a reserved keyword and before 21.05 we had an unquoted declaration of a column named offset) but kohastructure.sql is always ran so it's not a relevant example. Could there be a risk with the db revs on recent MariaDB versions warranting a CI job?