Skip to content

ci: drop the Sylius 2.3.0 workarounds now that 2.3.1 is out - #8

Merged
JDCyllene merged 1 commit into
CylleneDigital:mainfrom
JDCyllene:chore/sylius-2.3.1-workarounds
Oct 14, 2026
Merged

JDCyllene merged 1 commit into
CylleneDigital:mainfrom
JDCyllene:chore/sylius-2.3.1-workarounds

Conversation

@JDCyllene

Copy link
Copy Markdown
Member

What this pull request does

Sylius 2.3.1 passes the default label and icon of the grid delete action (Sylius#19285) and recognizes MariaDB on DBAL 4 in its migrations (Sylius#19272). The two workarounds they made necessary go away:

  • symfony/ux-twig-component is no longer capped below 3.5 in require-dev. Sylius 2.1 and 2.2 require 2.x, so the cap only mattered for 2.3, and 2.3.1 renders the delete buttons with 3.5 and later (checked with 3.6).
  • The MariaDB jobs run the migrations again instead of building the schema from the mappings (database_setup: schema removed, the action defaults to the migrations).
  • The docs restrict the MariaDB pitfall to Sylius 2.3.0 with DBAL 4 (Sylius 2.1 and 2.2 stay on DBAL 3) and advise upgrading to 2.3.1.

Points to watch

  • Tests pass (vendor/bin/phpunit, vendor/bin/behat --strict), locally on Sylius 2.3.1 / MySQL platform; the MariaDB migrations are validated by this CI
  • PHPStan and ECS are green
  • If the schema changed: a new migration is added, and sh tests/check-schema-drift.sh prints nothing (MySQL or PostgreSQL)
  • UPGRADE.md is up to date if the public contract changes (traits and interfaces, Twig hooks and functions, grid query)
  • A decision taken or reversed has its record in docs/adr/
  • No customer data, shop secrets or pre-production URLs appear in the code, the tests or this description

CI, development requirements and docs only: nothing changes in what a shop installs, no release needed.

Sylius 2.3.1 passes the default label and icon of the grid delete action (Sylius#19285) and
recognizes MariaDB on DBAL 4 in its migrations (Sylius#19272).

- symfony/ux-twig-component is no longer capped below 3.5 in require-dev: Sylius 2.1 and 2.2
  require 2.x, and 2.3.1 renders the delete buttons with 3.5 and later.
- The MariaDB jobs run the migrations again instead of building the schema from the mappings.
- The docs restrict the MariaDB pitfall to Sylius 2.3.0 with DBAL 4 (2.1 and 2.2 stay on DBAL 3)
  and advise upgrading to 2.3.1.
@JDCyllene
JDCyllene requested a review from a team as a code owner October 14, 2026 13:34
@JDCyllene
JDCyllene merged commit 920433b into CylleneDigital:main Oct 14, 2026
19 checks passed
@JDCyllene
JDCyllene deleted the chore/sylius-2.3.1-workarounds branch October 14, 2026 13:46
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.

1 participant