Appendix

Versioning of editable services

BaaS uses semantic versioning for editable services based on the industry-standard Major.Minor.Patch format, for example 1.0.0, 1.1.0, and 2.0.0. Semantic versioning improves control over changes and supports deployment of customized global package resources.

Understanding version numbers

Editable services follow the semantic versioning pattern Major.Minor.Patch.

• Major version (first digit): Introduces significant changes that break compatibility.
• Minor version (second digit): Adds new features or enhancements that maintain compatibility.
• Patch version (third digit): Includes bug fixes, minor adjustments, or customer-specific changes to standard content.

Version control by tenant type

The versioning behavior depends on whether the service content is originally created on an Infor-owned editor tenant or customized on a customer-owned target tenant.

Editor tenant (development environment)

In Global Packages, Infor controls the major and minor versions.

• Major version can be incremented, for example 1.0.0 to 2.0.0.
• Minor version can be incremented, for example 1.0.0 to 1.1.0.
• Patch version (third digit) cannot be modified by Infor and always remains 0.

Examples:

• Initial service creation: 1.0.0
• Add new features: 1.1.0
• Introduce major changes or deviations from the first version: 2.0.0

Target tenant (test or production environment) customization

Version control works differently for target tenants.

• Services are initially deployed through Global Packages from an editor tenant.
• Customizations to deployed services after downloading the service source code require incrementing the patch version.
• Only the patch version (third digit) can be modified in target tenants.
• Major and minor versions can be updated only by deploying a newer version through Global Packages.