Issue Task Resolved

#110351Raise symfony/property-info to 8.1.2

Stefan Bürk 08/01/26, 10:48 updated 08/01/26, 11:20

Description

The nightly builds of main fail again in the jobs “unit php 8.5 min” and
“unit php 8.5 min random” since 2026-08-01 (pipeline 105764, while 14.3 and
13.4 are green), with four failures in the Extbase ClassSchema tests:

bc. PropertyWithTypeDeclarationsTest::listWithSquareBracketsSyntaxProperty
PropertyWithTypeDeclarationsTest::listWithArraySyntaxWithoutKeyValueTypeProperty
PropertyWithoutTypeDeclarationsTest::listWithSquareBracketsSyntaxProperty
PropertyWithoutTypeDeclarationsTest::listWithArraySyntaxWithoutKeyValueTypeProperty

All four report “Failed asserting that actual size 1 matches expected size 2“
for the resolved collection key types.

These are exactly the tests adapted with issue #110325. The upstream fix
“Prevent PhpDocTypeHelper to wrongly assume keys type” shipped with
symfony/property-info v7.4.15 and makes the square bracket notation “Type[]“
and the array notation carrying only a value type resolve to a plain array
keyed by “int|string” instead of to a list. Since the
adapted expectations only hold with that version, #110325 raised the minimum
constraint to “^7.4.15” in the root manifest and in the Extbase manifest, the
only two declaring the component. That is required because the nightly “min“
jobs resolve from the constraint and not from the lock file.

The Symfony 8.1 upgrade (issue #109043) then replaced all symfony constraints
with “~8.1.0”, which silently dropped that minimum guarantee again. For this
component the 8.1 line publishes v8.1.0 (2026-05-29) and v8.1.2 (2026-07-22),
and only v8.1.2 contains the merged-up key type fix. The “max” jobs install
v8.1.2 and stay green, the “min” jobs install v8.1.0 and fail with the old,
wrong resolution.

The constraint must therefore be raised to “~8.1.2” in composer.json and in
typo3/sysext/extbase/composer.json. The lock file is already at v8.1.2, so only
its content hash changes. main is the only affected branch, 14.3 and 13.4 stay
on the 7.4 line and already carry the “^7.4.15” constraint.

Reviews 1

History 34

  1. Stefan Bürk commented and changed status Under Review Resolved done 0 % 100 % <span data-processor="relativetime" data-value="2026-08-01T11:20:10+00:00" > 08/01/26, 11:20 </span>

    Applied in changeset commit:d585ed6e8cef33572bd312f3cb6a9bd78238dad4.