Skip to content

Upload SP 11.14 RNs - #11751

Open
ConnorLand wants to merge 3 commits into
developmentfrom
ctl-Upload-11.14-SP-RNs
Open

Upload SP 11.14 RNs#11751
ConnorLand wants to merge 3 commits into
developmentfrom
ctl-Upload-11.14-SP-RNs

Conversation

@ConnorLand

Copy link
Copy Markdown
Collaborator

No description provided.

- Gradle 9.5.1 supports both Java 21 and 25. Java 25 requires Gradle 9.1+.
- Support for Java 21 is deprecated.

We recommend that projects and marketplace modules upgrade to Java 25.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚫 [vale] reported by reviewdog 🐶
[Mendix.Capitalization] Use ''Marketplace'' (capitalized)

- We added the ability to filter out the on disk changes on comparison pane.
- We introduced new fields to the package manifest of module packages. The manifest now indicates the type of the module (source, add-on, or solution) and whether the module contains extensions or AI skills. For more information, see [Package Manifest](/refguide/module-settings/#package-manifest).
- The `mx` command line tool's `show-module-version` and `set-module-version` commands now work for all modules in an app, instead of only protected (Add-on and Solution) modules. The System module remains excluded.
- The `mx` command line tool's `module-import` command now supports updating and replacing existing modules. Use `--import-mode update` to replace a module if it already exists in the app or add it if not, or `--import-mode replace` to replace an existing module and fail if it is not found. The default behavior (`--import-mode add`) is unchanged. Use `--conflict take_theirs` to overwrite an existing module without error, or `--conflict take_mine` to keep the existing module and skip the import silently. When replacing a module, use `--metadata take_existing` to copy the marketplace identity (guid, package id, version guid) from the existing module, `--metadata erase` to strip all identity fields, or the default `--metadata take_new` to take identity from the incoming module. In all cases, `AppStoreVersion` is taken from the incoming module and falls back to the existing value only when the incoming module does not provide one. A module that was previously obtained from the Marketplace always keeps its `FromAppStore` flag set to true regardless of the chosen strategy.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚫 [vale] reported by reviewdog 🐶
[Mendix.Capitalization] Use ''Marketplace'' (capitalized)

- We fixed an issue where Studio Pro would not update the Java proxies during deployment after renaming a Module. (Ticket #282363)
- We fixed an issue where expanding a folder in a document selector (for example while selecting a microflow, nanoflow, or JSON structure) would show it as expanded but without its contents. (Ticket #284451)
- We fixed an issue where the active document's tab could get scrolled out of view after opening many documents in a row.
- We fixed an issue where renaming in Studio Pro of e.g. a module or an entity could lead to consistency errors in Microflow expressions.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚫 [vale] reported by reviewdog 🐶
[Mendix.Latin] Use 'for example, ' instead of 'e.g. '.

- Fixed an issue where the content of the Microflow editor and Domain Model editor (Beta) canvas could appear blurry after scrolling or zooming.
- We fixed an issue where the "Push your changes" notification bar was incorrectly shown after a merge or cherry-pick that produced no actual model changes. Studio Pro now detects this scenario and shows an informational message instead.
- We fixed an issue where some grid cells in Studio Pro would become empty while scrolling the grid.
- Fixed an issue where concurrent git operations could fail with an "index is locked" error when the version control status bar polled for conflict information at the same time as write operations such as reset or checkout.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚫 [vale] reported by reviewdog 🐶
[Mendix.Capitalization] Use ''Git'' (capitalized)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants