Build numbers are now assigned automatically (LDEV-6516)

news
1

We changed how Lucee snapshot build versions are chosen on the 7.1 and 8.0 branches.

Previously someone bumped the fourth part of the version by hand in the project files for almost every snapshot. That meant a lot of “bump version” commits and made merging between branches harder.

What happens now

  • The version is still four parts: major.minor.patch.build, plus an optional suffix such as -SNAPSHOT or -RC.
  • The first three parts (for example 7.1.2 or 8.0.0) still live in the project files and only change when a new patch cycle starts.
  • When we push a change to the maintenance branch, our automated GitHub build picks the next build number and builds with that full version. After a successful publish it tags that commit.
  • Pull requests and forks do not use up those production build numbers.

Ticket: LDEV-6516
7.1: LDEV-6516 Let CI set the build number (7.1) by GianTschingt · Pull Request #2870 · lucee/Lucee · GitHub (follow-up LDEV-6516 Pass maven-settings.xml on SNAPSHOT deploy (7.1) by GianTschingt · Pull Request #2871 · lucee/Lucee · GitHub)

Gaps in the build number sequence

The build number moves forward for each build attempt on the branch—including builds that fail—so you may see gaps between published versions (for example 7.1.2.5 then 7.1.2.7 with no .6). That is expected. A missing number does not mean a release was removed; it usually means that build never finished or never published.

Local builds that do not go through that automated path keep a default like 7.1.2.0-SNAPSHOT / 8.0.0.0-SNAPSHOT unless you pass a full version yourself.

1 Like