From d8bb0d12b89b1cdfc32f363d0795c5a4b031fd1b Mon Sep 17 00:00:00 2001 From: Marks Troicins Date: Wed, 12 Aug 2026 11:39:28 +0200 Subject: [PATCH 1/2] [SOLP-3959] Document package manifest content identifiers (version-guid, module-type, content) --- .../modeling/app-explorer/modules/module-settings.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/content/en/docs/refguide/modeling/app-explorer/modules/module-settings.md b/content/en/docs/refguide/modeling/app-explorer/modules/module-settings.md index 6e69b4a6894..a163cf2696a 100644 --- a/content/en/docs/refguide/modeling/app-explorer/modules/module-settings.md +++ b/content/en/docs/refguide/modeling/app-explorer/modules/module-settings.md @@ -133,12 +133,17 @@ When you export a module package (a *.mpk* file), Studio Pro adds a `manifest.js * The module ID and module name * The module version * The checksum of the package +* A version GUID — a deterministic identifier derived from the checksum that uniquely identifies this specific build of the package +* The module type (`source`, `add-on`, or `solution`) +* The content types included in the package (for example, `extension` or `ai-skill`), if applicable * The Mendix metamodel version used to create the package * The list of files included in the package {{% alert type="info" %}} The legacy `package.xml` metadata file is not mentioned in `manifest.json` but is still included in the package for backward compatibility. -{{% /alert %}} +{{% /alert %}} + +If you try to import a module package that was created with a newer version of Studio Pro than the one you are using, Studio Pro shows an error and cancels the import. You need to upgrade to a compatible version of Studio Pro before importing the package. ## Read More From 003585df7bc687f5e0852541382ccb66a1ef2ad4 Mon Sep 17 00:00:00 2001 From: Quinn Tracy <142489060+quinntracy@users.noreply.github.com> Date: Tue, 18 Aug 2026 11:09:05 +0200 Subject: [PATCH 2/2] Review --- .../refguide/modeling/app-explorer/modules/module-settings.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/docs/refguide/modeling/app-explorer/modules/module-settings.md b/content/en/docs/refguide/modeling/app-explorer/modules/module-settings.md index 2e2e593c4e0..1f7540d368b 100644 --- a/content/en/docs/refguide/modeling/app-explorer/modules/module-settings.md +++ b/content/en/docs/refguide/modeling/app-explorer/modules/module-settings.md @@ -150,7 +150,7 @@ When you export a module package (a *.mpk* file), Studio Pro adds a `manifest.js * The module ID and module name * The module version * The checksum of the package -* A version GUID — a deterministic identifier derived from the checksum that uniquely identifies this specific build of the package +* A version GUID – a unique identifier for this build of the package, generated from its checksum * The module type (`source`, `add-on`, or `solution`) * The content types included in the package (for example, `extension` or `ai-skill`), if applicable * The Mendix metamodel version used to create the package @@ -160,7 +160,7 @@ When you export a module package (a *.mpk* file), Studio Pro adds a `manifest.js The legacy `package.xml` metadata file is not mentioned in `manifest.json` but is still included in the package for backward compatibility. {{% /alert %}} -If you try to import a module package that was created with a newer version of Studio Pro than the one you are using, Studio Pro shows an error and cancels the import. You need to upgrade to a compatible version of Studio Pro before importing the package. +If you try to import a module package that was created with a newer version of Studio Pro than the one you are using, Studio Pro shows an error and cancels the import. Upgrade to a compatible version of Studio Pro before importing the package. ### Location {#location}