Needs review
Project:
Field Validation
Version:
3.0.x-dev
Component:
Documentation
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
14 Aug 2026 at 09:58 UTC
Updated:
20 Sep 2026 at 10:04 UTC
Jump to comment: Most recent
Comments
Comment #2
abhisekmazumdarThis is a narrowed-down list to make the module as stable.
I have very little availability to work on all of it, but I still aim to get it done by next week.
If anyone can jump in and adjust the plan or help me move forward, it would be really helpful.
Comment #3
vidit.anjaria commentedComment #4
abhisekmazumdarComment #5
abhisekmazumdarComment #6
abhisekmazumdarSee the mentioned issues. They need testing and should be marked RTBC to move them forward.
Comment #7
ahmad-khalil-imagexComment #8
ahmad-khalil-imagexComment #9
arianraeesi commentedComment #10
abhisekmazumdarComment #11
abhisekmazumdarComment #13
abhisekmazumdarOpened MR !29, fixing four issues found while getting the module ready for RC needed before we mark it.
Found in our own pre-RC1 end-to-end test sweep:
Found by marcus_johansson's security review on
3.0.xthanks for running that:checkCondition()fatals when its condition references a missing field.Comment #15
abhisekmazumdarAll must-haves are in, and the pre-RC1 hardening pass (MR !29) is merged. Tagging a 3.0.0-rc1 release.
If anyone can test it end to end on a real site, that would help a lot the more real-world coverage before final, the better. Aiming to move to a stable 3.0.0 release next if no blockers turn up.
Comment #16
abhisekmazumdarA new bug came in for 3.0.x
#3622470: Update symfony/intl to v7 (compatibility with drupal11 & symfony 7)
Comment #17
abhisekmazumdarI have to postpone the stable release until next month. I'll be unavailable for a week this month end, and I don't want to make a release and disappear. So the new plan is to make the stable release first thing next month, so I can handle anything that comes up if needed.
Comment #18
arianraeesi commented