Repository navigation
ci: bump BuildTestAppAction to 4.3.1 and build the MariaDB schema from the mappings - #12
Merged
JDCyllene merged 1 commit intoOct 13, 2026
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps
SyliusLabs/BuildTestAppActionto v4.3.1 (c3b108b5f3c299c55f429a8cf0ed88734d4f4979, the commit the tag points at).v4.3.1 writes
serverVersion=11.4.0-MariaDBinDATABASE_URLfor MariaDB, where v4.3.0 wroteserverVersion=11.4. DBAL therefore picks the MariaDB platform, and under DBAL 4 the Sylius migrations skip themselves on it (isMySql()is false,MariaDBPlatformno longer extendsMySQLPlatform). The database stays empty andsylius:fixtures:loadfails on a missing table, which is what turned #10 red on the MariaDB job.The MariaDB job now passes
database_setup: schema, so the action builds the schema withdoctrine:schema:updateinstead of the migrations. The plugin has neither entity nor migration, so nothing of its own goes untested. Every other job keeps running the migrations.The MariaDB job of this pull request is what validates the change.
Supersedes #10.