Skip to content

Update module versioning guidelines in documentation #11704

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
quinntracy merged 2 commits into from
Aug 12, 2026
Merged

Update module versioning guidelines in documentation #11704

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
19ee3d1
Update module versioning guidelines in documentation
tknippenberg Aug 11, 2026
210a963
Review
quinntracy Aug 12, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion content/en/docs/refguide/modeling/app-explorer/modules/module-settings.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -74,7 +74,7 @@ This is the version number of the module which is shown in various places in the
When redistributing a module, you should always change the version number when changes are made. For modules that will be published to the Marketplace, the version must be set before exporting the package.

{{% alert color="info" %}}
The Marketplace automatically uses the version from the exported package. You cannot change this manually. If the version is already in use, the Marketplace rejects the package.
Marketplace automatically uses the version from the exported package for packages exported from Studio Pro 11.12 and above. You cannot change this manually. If the version is already in use, the Marketplace rejects the package.
{{% /alert %}}

#### Version format
Expand All @@ -88,6 +88,10 @@ Refer to the following guidance when changing the version number:

Next to the numerical major, minor and patch version, alphanumerical characters are allowed. This is considered to be an advanced feature, for more information, please see [Semantic Versioning](https://semver.org/). An example of an advanced version number is *1.3.7-beta.2*.

{{% alert color="warning" %}}
Mendix Marketplace does not support module packages with alphanumerical characters in the version number. To publish on Marketplace, the version number should consist of three numerical parts. Support for alphanumerical characters will be added in a future release.
{{% /alert %}}

## Package {#package}

{{% alert color="info" %}}
Expand Down