The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.Problem/Motivation
4.x has been created here, as it seems: #3346050: Change CAPTCHA from ^1.4 to ^1.4 || ^2 in composer.json file
But it is listed as stale: https://git.drupalcode.org/project/recaptcha/-/branches/stale and there was only that one commit.
I'd suggest we remove 4.x for now, until we have done all the RTBC'd fixes in 8.x-3.x and afterwards we can discuss creating a new 4.x default branch. Otherwise, it will just be a lot more work?
Another alternative would be to use 4.x for #2493183: Ajax support / Use behaviors which is a risky large change.
What would you prefer @liam.morland?
We should have as less work with it as possible or for good reasons!
Comments
Comment #2
liam morland4.x just points to 8.x-3.2. I think we should leave it or delete it if we can. When a new major release branch is needed, it should be 4.0.x.
Comment #3
anybody@Liam Morland thanks, I agree. Just tried to delete 4.x but it's not possible: "Prevented by server hooks". Do you see any chance or would like to try as maintainer?
Seems like we can't delete it anymore: https://www.drupal.org/project/recaptcha/releases/4.x-dev
So that's a bit confusing, especially in issues where 4.x can be selected. -.-
Comment #4
liam morlandThe release node for it has to be deleted first. Make a request on the Drupal.org infrastructure queue.
Comment #5
anybody@Liam Morland thank you, I did so: #3410317: Delete release node for recaptcha 4.x
Comment #6
anybodyOkay so we'll keep that branch and switch to semver.
I'd say we should merge the RTBC'd (or simple to review) issues into 3.x and afterwards use 4.x as default branch.
There we should focus on finishing #2493183: Ajax support / Use behaviors. Once we have a 4.0.0 release, 3.x should not be recommended anymore.
Comment #7
liam morland