Needs work
Project:
Project Browser
Version:
2.1.x-dev
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Reporter:
Created:
17 Dec 2025 at 22:07 UTC
Updated:
17 Dec 2025 at 23:29 UTC
Jump to comment: Most recent
Yep, it's broken because of upstream changes in Symfony's validation system that are in 11.3. You have to explicitly configure constraints, you can't just hope that options land in the correct place.
It's a one-line fix, but Drupal CMS will not install at all right now on 11.3.0. It breaks with:
Error: Unknown named parameter $value in Drupal\Core\Validation\ConstraintFactory->createInstance()
This needs to be quickly fixed in Project Browser and a patch release rolled for both the 2.0.x and 2.1.x lines.
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #3
phenaproximaOver to @tim.plunkett for the fastest commit and release in Project Browser history, probably.
Comment #4
tim.plunkettMerging next
Comment #5
phenaproximaThe question, of course, is "Why didn't we catch this?"
I think the answer is:
After this is merged, we are going to keep it open for tests. The tests will probably consist of opting all our existing tests into strict config validation, and fixing any failures that arise. (Core tests are opted into strict validation by default; contrib tests have to opt in explicitly, if I remember correctly. I believe there is a change record for this, I'll look for it.)
Comment #6
phenaproximaFound it: https://www.drupal.org/node/3362879
Comment #8
phenaproximaSelf-assigning for test coverage so we can catch stuff like this.