feat: Add `builds next` option #9946

neznaika0 · 2026-02-11T19:50:24Z

Description

A small improvement to upgrade to the dev branch: 4.7 | dev-develop | 4.8-dev

Checklist:

Securely signed commits
Component(s) with PHPDoc blocks, only if necessary or adds value (without duplication)
Unit testing, with >80% coverage
User guide updated
Conforms to style guide

michalsn

I'm not a big fan of introducing next, as it will require an update that we will most likely forget to make.

Additionally, removing the instructions on how to adjust the composer file manually will leave people clueless about what to do.

I would agree to introducing something like allowing a version number to be specified, for example: 4.8, 4.9, etc., which would result in a proper, explicit change - but this parameter would need to come with a detailed explanation.

neznaika0 · 2026-02-12T07:15:11Z

We have a workflow for the appstarter release. What if I replace the constant for task?

Honestly, I do not know if anyone uses the dev version except me.

If we continue, it is advisable to specify the next CI version with the release. Because the dev has the current number 4.7.0. In fact, it's 4.7.1 or 4.8.0. module-manager won't forgive this.

michalsn · 2026-02-12T07:23:00Z

We have a workflow for the appstarter release. What if I replace the constant for task?

If the version can be adjusted automatically for the next minor release, then I would accept this.

Honestly, I do not know if anyone uses the dev version except me.

Yes, it's used.

If we continue, it is advisable to specify the next CI version with the release. Because the dev has the current number 4.7.0. In fact, it's 4.7.1 or 4.8.0.

Not sure about it. As it could lead to a situation where someone thinks they are using version ie, 4.8, which is not the "real" version 4.8.

neznaika0 · 2026-02-12T07:28:04Z

I understand, that's why I indicated the note in the manual.
I manually changed the version in vendor/ to work.

neznaika0 · 2026-02-12T07:47:20Z

Paste here?
https://github.com/codeigniter4/CodeIgniter4/blob/develop/admin/prepare-release.php
We are creating a new 4.8.0.rst if it is automatic? take the logic of the minor version from there.
Another way is to add to the description of the release steps

michalsn

Looks good.

paulbalandan · 2026-02-12T17:18:09Z

admin/starter/builds

-define('LATEST_RELEASE', '^4.0');
+define('LATEST_RELEASE', '^4.7');
+define('DEVELOP_BRANCH', 'dev-develop');
+define('NEXT_MINOR', '^4.8-dev');


Is caret allowed by composer for dev versions? I think this should be 4.8.x-dev here and in the release script?

I performed composer update and it did not cause any errors. I'll delete the symbol, it's more correct this way.

paulbalandan · 2026-02-12T17:20:00Z

admin/prepare-release.php

 $minor        = $versionParts[0] . '.' . $versionParts[1];

+// Note: Major version will change someday (4.x..5.x) - update manually.
+$nextVersion = $versionParts[0] . '.' . $versionParts[1] + 1;


$nextMinor should be more appropriate name here

paulbalandan · 2026-02-12T17:22:03Z

admin/RELEASE.md

      and `<version number="4.x.x">`
+    * Update **admin/starter/builds**:
+      * Set `define('LATEST_RELEASE', '^4.x')`
+      * Set `define('NEXT_MINOR', '^4.y-dev')`.


See previous comment.

paulbalandan · 2026-02-12T17:23:20Z

admin/RELEASE.md

+    * Update **admin/starter/builds**:
+      * Set `define('LATEST_RELEASE', '^4.x')`
+      * Set `define('NEXT_MINOR', '^4.y-dev')`.
+      * If the major version changes, you need to manually change to `define('NEXT_MINOR', '^5.0-dev')`.


On a semver perspective, 5.0 is not really next minor but next major. Maybe add a note instead to define a NEXT_MAJOR constant when time comes?

How will it work? If we create a v5.0, how do we determine that it 5.0-dev needs to be inserted and not 4.y-dev?

paulbalandan · 2026-02-12T17:23:58Z

user_guide_src/source/changelogs/v4.7.1.rst

+Others
+======
+
+- **builds:** In the ``builds`` script (for ``codeigniter4/appstarter``), the ``next`` option has been added


Not an option but an argument (since no preceding dashes).

paulbalandan · 2026-02-12T17:24:25Z

user_guide_src/source/changelogs/v4.7.1.rst

+======
+
+- **builds:** In the ``builds`` script (for ``codeigniter4/appstarter``), the ``next`` option has been added
+  to switch ``4.7.x`` to the next minor version ``4.8-dev``. See :ref:`Latest Dev<switch-to-dev-version>`.


Suggested change

to switch ``4.7.x`` to the next minor version ``4.8-dev``. See :ref:`Latest Dev<switch-to-dev-version>`.

to switch ``4.7.x`` to the next minor version ``4.8.x-dev``. See :ref:`Latest Dev<switch-to-dev-version>`.

Why not 4.8-dev? composer successfully download the branch

paulbalandan · 2026-02-12T17:28:27Z

user_guide_src/source/installation/installing_composer.rst

 Note that this differs from the released user guide, and will pertain to the
 develop branch explicitly.

+.. note:: You should not rely on the version of the framework in your project


Off-topic for another PR, maybe? Should "unstable" versions have a suffixed -DEV on the version number? Like for develop branch it would be the next patch 4.7.1-DEV while 4.8 branch is 4.8-DEV? @michalsn ?

Seems like version_compare() would handle this without a problem, so if we can automate this, then why not? Without automation, we would probably forget about it in a few weeks.

feat: Add builds next option

5db78bf

michalsn reviewed Feb 12, 2026

View reviewed changes

fix: Add release changes for builds

f5634b9

neznaika0 requested a review from michalsn February 12, 2026 09:36

michalsn approved these changes Feb 12, 2026

View reviewed changes

paulbalandan reviewed Feb 12, 2026

View reviewed changes

fix: Apply suggestions

9e5bda7

	to switch ``4.7.x`` to the next minor version ``4.8-dev``. See :ref:`Latest Dev<switch-to-dev-version>`.
	to switch ``4.7.x`` to the next minor version ``4.8.x-dev``. See :ref:`Latest Dev<switch-to-dev-version>`.

feat: Add builds next option #9946

Are you sure you want to change the base?

feat: Add builds next option #9946

Conversation

neznaika0 commented Feb 11, 2026

Uh oh!

michalsn left a comment

Choose a reason for hiding this comment

Uh oh!

neznaika0 commented Feb 12, 2026

Uh oh!

michalsn commented Feb 12, 2026

Uh oh!

neznaika0 commented Feb 12, 2026

Uh oh!

neznaika0 commented Feb 12, 2026

Uh oh!

michalsn left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

feat: Add `builds next` option #9946

feat: Add `builds next` option #9946