Merge branch 'mendix:development' into run/5208-update-offline-docs-for-java-update-tool

Author: emirmx

.claude/settings.json

@@ -6,11 +6,11 @@
     "AWS_PROFILE": "my-sandbox",
     "AWS_REGION": "eu-central-1",
     "CLAUDE_CODE_USE_BEDROCK": "1",
-    "ANTHROPIC_MODEL": "eu.anthropic.claude-sonnet-4-5-20250929-v1:0",
+    "ANTHROPIC_MODEL": "eu.anthropic.claude-sonnet-4-6",
     "ANTHROPIC_SMALL_FAST_MODEL": "eu.anthropic.claude-haiku-4-5-20251001-v1:0",
     "ANTHROPIC_DEFAULT_HAIKU_MODEL": "eu.anthropic.claude-haiku-4-5-20251001-v1:0",
-    "ANTHROPIC_DEFAULT_OPUS_MODEL": "eu.anthropic.claude-opus-4-6-v1",
-    "ANTHROPIC_DEFAULT_SONNET_MODEL": "eu.anthropic.claude-sonnet-4-5-20250929-v1:0",
+    "ANTHROPIC_DEFAULT_OPUS_MODEL": "eu.anthropic.claude-opus-4-8",
+    "ANTHROPIC_DEFAULT_SONNET_MODEL": "eu.anthropic.claude-sonnet-4-6",
     "DISABLE_PROMPT_CACHING": "0",
     "CLAUDE_CODE_MAX_OUTPUT_TOKENS": "10240",
     "MAX_THINKING_TOKENS": "1024"

.github/workflows/vale.yml

@@ -1,6 +1,6 @@
 name: Vale Linting
 
-# Trigger on PRs that change Markdown files
+# Trigger on PRs that change Markdown files (but skip run on draft PRs)
 on:
   pull_request:
     types: [opened, synchronize, reopened, ready_for_review]

content/en/docs/apidocs-mxsdk/apidocs/marketplace/_index.md

@@ -0,0 +1,11 @@
+---
+title: "APIs for Marketplace"
+url: /apidocs-mxsdk/apidocs/apis-for-marketplace/
+type: swagger
+no_list: false
+description_list: true
+description: "Provides the documentation of APIs for Marketplace."
+linktitle: "Marketplace"
+---
+
+Mendix offers the following APIs for Marketplace:

…ocs/apidocs-mxsdk/apidocs/content-api.md …mxsdk/apidocs/marketplace/content-api.mdcontent/en/docs/apidocs-mxsdk/apidocs/content-api.md renamed to content/en/docs/apidocs-mxsdk/apidocs/marketplace/content-api.md content/en/docs/apidocs-mxsdk/apidocs/content-api.md renamed to content/en/docs/apidocs-mxsdk/apidocs/marketplace/content-api.md

@@ -1,11 +1,10 @@
 ---
-title: "Content API"
-linktitle: "Marketplace Content"
+title: "Marketplace Content API"
 url: /apidocs-mxsdk/apidocs/content-api/
 type: swagger
 description: "The Content API accesses both public and company-specific Marketplace content information."
 restapi: true
-weight: 45
+weight: 10
 ---
 
 ## Introduction
@@ -22,7 +21,7 @@ If you have Marketplace content, this API can help you get the following informa
 
 ### Generating a PAT
 
-For details on how to generate a PAT, see the [Personal Access Tokens](/portal/user-settings/#pat) section of *User Settings*.
+For details on how to generate a PAT, refer to the [Personal Access Tokens](/portal/user-settings/#pat) section of *User Settings*.
 
 Select at least the following as the **Marketplace** scope:
 
@@ -39,7 +38,7 @@ GET /content HTTP/1.1
 Authorization: MxToken 7LJE…vk
 ```
 
-To authenticate calls when using the OpenAPI specification below, click **Authorize** and use the value `MxToken {GENERATED_PAT}`.
+To authenticate calls when using the OpenAPI specification included in the next section, click **Authorize** and use the value `MxToken {GENERATED_PAT}`.
 
 ## API Reference
 

content/en/docs/apidocs-mxsdk/apidocs/marketplace/publish-api.md

@@ -0,0 +1,44 @@
+---
+title: "Marketplace Publish API"
+url: /apidocs-mxsdk/apidocs/publish-api/
+type: swagger
+description: "The Publish API accesses both public and company-specific Marketplace content information."
+restapi: true
+weight: 20
+---
+
+## Introduction
+
+The Marketplace Publish API allows you to manage the releases of your Marketplace components. It provides endpoints to create new releases with version metadata, upload source files, check release status as it moves through review and publication workflows, and unpublish releases when needed.     
+The API handles both public and private components.
+
+{{% alert color="warning" %}}
+You can currently only publish new releases of existing components.
+{{% /alert %}}
+
+## Authentication {#authentication}
+
+### Generating a PAT
+
+For details on how to generate a PAT, refer to the [Personal Access Tokens](/portal/user-settings/#pat) section of *User Settings*.
+
+Select at least the following as the **Marketplace** scope:
+
+* `mx:marketplace:write`
+
+Store the generated value `{GENERATED_PAT}` somewhere safe so you can use it to authorize your Content API calls.
+
+### Using the PAT
+
+Each request must contain an `Authorization` header with the value `MxToken {GENERATED_PAT}`. Here is an example:
+
+```http
+GET /content HTTP/1.1
+Authorization: MxToken 7LJE…vk
+```
+
+To authenticate calls when using the OpenAPI specification included in the next section, click **Authorize** and use the value `MxToken {GENERATED_PAT}`.
+
+## API Reference
+
+{{< swaggerui-disable-try-it-out src="/openapi-spec/marketplace-publish.yaml"  >}}

content/en/docs/apidocs-mxsdk/apidocs/studio-pro-11/pluggable-widgets/_index.md

@@ -69,7 +69,8 @@ A widget package file is just a ZIP archive containing the following things:
     * *{widgetName}.tile.png* sets the tile image inside the Studio Pro toolbox in tile view (the ideal image size is 256x192 pixels, but other sizes will be resized to fit)
     * *{widgetName}.tile.dark.png* sets the dark-mode equivalent to *{widgetName}.tile.png*
 * Optionally, some widget-related resources, preferably located next to the file which contains the client component
-    * Note that all CSS files you add (except the one located in the **lib** sub-directory) will automatically be loaded in an app via the widget
+    * All CSS files you add (except the ones located in the **lib** sub-directory) will automatically be loaded in an app via the widget.
+    * When the React client is enabled for an app, any `assets` directories in a widget package are automatically copied to the widget's directory under `dist` during bundling. This ensures that all asset files from a pluggable widget are included in the final build and available at runtime.
 
 Naming your widget package file after the `widgetName` is best practice. Also, a widget package can include multiple widgets by putting several of the above items in the same widget package. However, creating such packages is *not recommended*. 
 

content/en/docs/apidocs-mxsdk/apidocs/studio-pro-11/pluggable-widgets/pluggable-widgets-client-apis/_index.md

@@ -2,7 +2,7 @@
 title: "Client APIs"
 linktitle: "Client APIs for Pluggable Widgets"
 url: /apidocs-mxsdk/apidocs/pluggable-widgets-client-apis/
-description: A guide for understanding the client APIs available to pluggable widgets in Mx10.
+description: A guide for understanding the client APIs available to pluggable widgets.
 weight: 20
 aliases:
     - /apidocs-mxsdk/apidocs/client-apis-for-pluggable-widgets

content/en/docs/apidocs-mxsdk/apidocs/studio-pro-11/pluggable-widgets/pluggable-widgets-client-apis/pluggable-widgets-client-apis-list-values.md

@@ -1,7 +1,7 @@
 ---
 title: "List Values"
 url: /apidocs-mxsdk/apidocs/pluggable-widgets-client-apis-list-values/
-description: A guide to understanding the list of objects for the datasource property in Mx10.
+description: A guide to understanding the list of objects for the datasource property.
 ---
 
 ## Introduction

content/en/docs/apidocs-mxsdk/apidocs/studio-pro-11/pluggable-widgets/pluggable-widgets-property-types.md

@@ -480,10 +480,12 @@ Then the Studio Pro UI for the property appears like this:
 
 The action property type allows a user to configure an action which can do things like call nanoflows, save changes, and open pages.
 
-If a `dataSource` attribute is not specified, the client will receive an `ActionValue` representing the action or `undefined` if the **Do nothing** action was selected.
+If a `dataSource` attribute is not specified, the client will receive an [`ActionValue`](/apidocs-mxsdk/apidocs/pluggable-widgets-client-apis/#actionvalue) representing the action or `undefined` if the **Do nothing** action was selected.
 
 When a `dataSource` attribute is specified and configured by the user, it is passed as a [`ListActionValue`](/apidocs-mxsdk/apidocs/pluggable-widgets-client-apis-list-values/#listactionvalue). For more information, see the [Datasource](#datasource) section below.
 
+Action properties can be preconfigured using the `defaultValue` and `defaultType` attributes. This is particularly useful when the widget is intended to be used with a specific microflow, nanoflow, or page. When the property [exposes action variables](#action-xml-elements), they are automatically mapped to parameters of matching name and type.
+
 #### XML Attributes {#xml-attributes}
 
 | Attribute      | Required | Attribute Type | Description                                                                                             |
@@ -496,7 +498,7 @@ When a `dataSource` attribute is specified and configured by the user, it is pas
 
 #### XML Elements {#action-xml-elements}
 
-`<actionVariables>` — Defines variables a widget provides when calling [execute() on an ActionValue](/apidocs-mxsdk/apidocs/pluggable-widgets-client-apis/#execute). The variables are made available in Studio Pro when configuring [Call a Microflow](/refguide/on-click-event/#call-microflow) and [Call a Nanoflow](/refguide/on-click-event/#call-nanoflow) actions.
+`<actionVariables>` — Defines variables a widget provides when calling [execute() on an ActionValue](/apidocs-mxsdk/apidocs/pluggable-widgets-client-apis/#execute). The variables are made available in Studio Pro when configuring [Call a Microflow](/refguide/on-click-event/#call-microflow) and [Call a Nanoflow](/refguide/on-click-event/#call-nanoflow) actions. Action variables are automatically mapped to parameters of the same name (`key`) and type.
 
 `<actionVariable>` (required one or more) — Represents a primitive value provided by the widget as an argument when calling `ActionValue.execute()`. The variable is defined by the following attributes:
 

content/en/docs/community-tools/contribute-to-mendix-docs/style-guide/product-naming-guide.md

@@ -132,20 +132,6 @@ A solution for an air-gapped secure Mendix deployment.
 
 This section contains various Mendix terms that are used in the product UI and documentation.
 
-### application & app
-
-An "application" or "app" can be one of the following:
-
-* A local application
-* A Free App
-* A licensed application hosted on Mendix Cloud; another cloud such as AWS, SAP Cloud, or IBM Cloud Portal; or on the user's own server
-
-Do not capitalize (meaning, do not write "Mendix App").
-
-Do not replace with "app project" (or "project") generically, even when referring to project management-like tasks. **Project** is still used in some UI text, but that usage is being phased out. Using "app" in all instances is prioritized.
-
-The full word "application" has a more well-rounded meaning to it (as in, web and mobile apps), whereas "app" may suggest just mobile apps to the reader. Accordingly, it can be better to use "application" at the beginning of documents and then switch to "app" later on. We want to make it clear that Mendix is not just for building mobile apps, but all kinds of applications.
-
 ### App ID
 
 Always capitalize.