Versioning#

Since 26.4, the nplus version is independent of the nscale version. All nplus charts — the instance, the environment, the cluster and every component — carry the same nplus version. Which nscale version runs is decided by the values, not by the chart version.

nplus versions#

• X.Y is the release line. It follows the calendar: 26.4 is the line of 2026. A new line starts when the chart code changes in a way that needs attention on upgrade.
• rev counts the releases of a line, starting at 1000. Every published version passed the full test suite.
• Development versions are pre-releases of the next release in SemVer terms (26.4.1000-2 < 26.4.1000), so helm install without --devel never picks one up.

Versions before 26.3 followed the nscale Application Layer version (for example 10.2.1002-200). They remain available, but receive no updates. 26.3.200 is exactly the code of beta 200 under the new number: switch to it first, without any change to your deployment, and move on to 26.4 from there.

nscale versions#

Every chart release ships with the latest nscale version as its default: image tags, image names and global.meta.nscaleVersion point to it, and the chart’s appVersion shows it (helm list displays both versions).

To run a different nscale version, stack its version file on top of your values. The version files set the image of every component plus the nscale version shown in the operator:

helm upgrade -i demo nplus/nplus-instance \
  --version 26.4.1000 \
  --values my-instance.yaml \
  --values versions/10.1.1509.yaml

The version files are published alongside the charts (see the versions folder). Do not set single image.tag values by hand: a newer component rejects an older license (The license version is not supported), and a partial pin is outdated with the next release.

The latest chart code works with the latest nscale version and all versions below (since 8.0, the first container release).

Best practice#

• Pin the nplus version (--version 26.4.1000) and, if you need a specific nscale version, the version file.
• Upgrading nplus and upgrading nscale are two separate steps: first the chart with the same version file, then the version file. Without a version file, a chart upgrade also moves nscale to the latest version.
• Use --devel only for test environments.

You can query available versions with helm search repo nplus --versions (add --devel to include development versions).