Problem/Motivation

In the 11.x branch, we currently have

const VERSION = '11.3-dev';

in Drupal.php.

But AFAICS this is the branch from where next minor 11.4 will be released, right?

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

Introduced terminology

API changes

Data model changes

Release notes snippet

Issue fork drupal-3569169

Command icon Show commands

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:

About issue forks

Comments

mondrake created an issue. See original summary.

jonathan1055 made their first commit to this issue’s fork.

jonathan1055 opened merge request !14469

jonathan1055’s picture

jonathan1055 commented

@mondrake Thinking about this again, is this actually a problem? I'm not saying yes or no, I'm saying I don't know.

The 11.3.x branch was created in October 2025
https://www.drupal.org/project/drupal/releases/11.3.x-dev

Maybe the constant VERSION = '11.3-dev' remains like in the 11.x branch until 11.4.x-dev is created? That has not happened yet.

longwave’s picture

longwave
he/him
Primary language English
Location UK
commented
Status: Active » Reviewed & tested by the community

We have had this issue before, since we moved to the 11.x branch I don't think our branching script has kept up with changing this: #3487150: \Drupal::VERSION on 11.x not correct

I think we should do this because 11.x will eventually be branched and become 11.4.x, it currently contains more, newer code than 11.3.x does so calling it 11.3 is technically incorrect. Once 11.4.x is branched we should try to remember to update 11.x to be 11.5 as well.

Therefore marking this as RTBC. However I don't think this is much of a problem in practice, because the constant is only used internally - Composer and packagist go by the branch name for dev versions.

jonathan1055’s picture

jonathan1055 commented

Thank you. It helps in Contrib pipelines, even if it does not make a technical difference, this value is displayed in the log when running "next minor". We have the 'current' variant running 11.3.2 and 'next minor' shows 11.3-dev whereas people then get confused as they were expecting it to show 11.4-dev

Just for the record, the "current" contrib variant job log shows

drupalConstraint=11.3.2 (from DRUPAL_CORE)
Drupal installed version: 11.3.2

and the "next minor" variant shows

drupalConstraint=11.x-dev (from DRUPAL_CORE)
Drupal installed version: 11.3-dev
mondrake’s picture

mondrake
Location 🇮🇹
commented

#6 +1

  • catch committed ecd23b04 on 11.x 
    fix: #3569169 Wrong VERSION in 11.x

By: mondrake
By: jonathan1055
By:...

catch closed merge request !14469

catch’s picture

catch
he/him
Primary language English
commented
Status: Reviewed & tested by the community » Fixed

Committed/pushed to 11.x, thanks!

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

jonathan1055’s picture

jonathan1055 commented
Title: Wrong VERSION in 11.x » Wrong const VERSION in 11.x (11.3-dev should be 11.4-dev)

Thank you @catch. Yes, just confirming that it is fixed now, a pipeline from today shows

drupalConstraint=11.x-dev (from DRUPAL_CORE)
Drupal installed version: 11.4-dev

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.