Project versioning
Manage project versions to simplify release creation.
Project versioning streamlines version management by reducing manual Git and manifest updates, improves version visibility, and helps prevent errors through validation and compatibility checks.
When you create a version, the system:
- Uses your current branch as the base branch.
- Updates the project version in the manifest file.
- Creates or updates the appropriate release branch.
- Pushes the versioned state to the remote repository.
You can create project versions by using the UI or API. For more information, see Creating project versions and Versioning projects.
Creating a version from a non-release branch
Creating a version from a non-release branch (for example, main) creates a
release for the current version and updates the base branch to the new version.
Creating a version from a release branch
If the base branch is a release branch, creating a new version creates a new release branch and does not update the base release branch, unlike the behavior with a non-release base branch.
Including local changes
You can choose whether local changes are included during the version creation process. The following options are available:
- Do not include uncommitted changes
- Include all changes
Project versioning usage guidelines
Target runtime version
When you add a package to a project, a warning is displayed if the package targets a higher server version than the project package, as follows.
- Project target server version: 12.1
- Package target server version: 13.0
The warning indicates that the added package might rely on capabilities that are not available in the project’s target server version. You can still decide whether to proceed, but compatibility issues might occur.