Software Updates & Version Support Policy

If you require any more information or have any questions about this Policy, please feel free to contact us through the contact form or by email at support@blisk.io.

1. Purpose

This policy defines how Blisk versions are supported, updated, and retired. Its goal is to ensure high software quality, faster innovation, and a secure, predictable experience for all users.

By focusing support on the most recent releases, Blisk can deliver new features faster, reduce defects, and maintain compatibility with modern web technologies.

2. Software Versioning Scheme

Blisk uses a four-part versioning format:

MAJOR.MINOR.PATCH.BUILD

Example: 25.0.115.28

Each part of the version number has a specific meaning and indicates the scope and impact of changes in a release.

Major Version

Format: MAJOR.x.x.x

The major version represents significant product changes that may affect behavior, compatibility, or supported features.

Major versions may include:

Large feature introductions or architectural changes
Removal or deprecation of legacy functionality
Changes that may require user action or updates to workflows
Updates aligned with major platform or engine upgrades

Only the current and previous major versions are supported, as defined in this policy.

Minor Version

Format: x.MINOR.x.x

The minor version indicates notable improvements that are backward-compatible within the same major version.

Minor versions may include:

New features and enhancements
Performance improvements
UI and usability updates
Non-breaking behavior changes

Minor updates do not affect version support status.

Patch Version

Format: x.x.PATCH.x

The patch version represents maintenance updates focused on stability and correctness.

Patch versions typically include:

Bug fixes
Security fixes
Reliability and crash fixes
Small behavior corrections without functional changes

Patch updates are backward-compatible and do not introduce new features.

Build Version

Format: x.x.x.BUILD

The build version identifies a specific compiled build of the application.

Build versions may differ due to:

Platform-specific builds (Windows, macOS, Linux)
Internal build system changes
Packaging or distribution updates
Emergency rebuilds without code changes

Build numbers do not affect compatibility, feature availability, or support status.

Version Support Scope

Version support is determined only by the MAJOR version
Minor, patch, and build versions inherit the support status of their major version
Updating within the same major version does not impact license validity or support eligibility

Backward Compatibility

Blisk strives to maintain backward compatibility within a major version
Compatibility across major versions is not guaranteed
Users are encouraged to review release notes when upgrading between major versions

3. Supported Versions

Blisk officially supports only the two most recent major versions of the application at any given time:

The current production major version
The previous major version

All other versions are considered unsupported, regardless of their minor, patch, or build number.

Definition of a Supported Major Version

A major version is identified by the first number in the version string.

Example:
Current production version: 25.0.115.28
→ Major version: 25

Version	Support status
25.1.0.0	Supported
25.0.0.0	Supported
24.1.0.0	Supported
24.0.0.0	Unsupported
23 and earlier	Unsupported

Only the current and previous major versions are supported. All earlier major versions are unsupported, regardless of their minor, patch, or build number.

4. Unsupported Versions

Once a new major version is released, any version more than one major release behind becomes unsupported (see Definition of a Supported Major Version above).

Starting from the effective date of this policy, unsupported versions will:

Stop receiving updates
Stop receiving bug fixes and security patches
Lose access to Premium license features
(Premium licenses will not function on unsupported versions)

Blisk makes no guarantees regarding stability, security, or compatibility of unsupported versions.

5. Premium License Enforcement

Premium licenses are valid only on supported versions of Blisk.

Running an unsupported version may result in Premium features being disabled
Updating to a supported version restores Premium functionality automatically

This enforcement ensures licensing integrity and consistent product behavior.

6. Update Availability & Delivery

Blisk releases updates that may include new features, performance improvements, bug fixes, and security patches
Updates are available via the official Update Center
Users are responsible for installing updates to remain on a supported version