From 776c228a78949e8a5daccbaf062726dd5c8065f3 Mon Sep 17 00:00:00 2001 From: Cristian Date: Mon, 9 Feb 2026 12:01:35 -0300 Subject: [PATCH 1/3] W-21199055-Create-MinMuleRuntimeVersion-note-CP --- modules/ROOT/pages/int-versions.adoc | 2 ++ 1 file changed, 2 insertions(+) diff --git a/modules/ROOT/pages/int-versions.adoc b/modules/ROOT/pages/int-versions.adoc index 5b7f04f0f..3cca5d3b6 100644 --- a/modules/ROOT/pages/int-versions.adoc +++ b/modules/ROOT/pages/int-versions.adoc @@ -44,6 +44,8 @@ Version settings are important in several scenarios: * Adding a version of Mule or Java that is missing from your project * Selecting versions of Mule or Java that are compatible with each other +NOTE: Changing the minimum Mule version (`minMuleVersion`) manually can have serious implications. This requires a full test of your application so it works correctly with the target Mule runtime. Newer Mule runtimes turn on feature flags by default and can change behavior that was fixed in later versions. Your application can rely on behavior that was later corrected or on a previous issue. Prefer changing the Mule version through *Project Properties*, and always run full regression tests after any version change. + When a Mule or Java version isn't set for a project, the IDE's canvas and notifications provide a *Set version* button that opens the *Project Properties* tab. You can also navigate directly to the *Project Properties* tab. From 5928fcb63dc89a03e6b66f7a4ef295fe2afdfc8d Mon Sep 17 00:00:00 2001 From: Cristian Date: Mon, 9 Feb 2026 12:03:09 -0300 Subject: [PATCH 2/3] W-21199055-Fix-format-CP --- modules/ROOT/pages/int-versions.adoc | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/modules/ROOT/pages/int-versions.adoc b/modules/ROOT/pages/int-versions.adoc index 3cca5d3b6..d91532e83 100644 --- a/modules/ROOT/pages/int-versions.adoc +++ b/modules/ROOT/pages/int-versions.adoc @@ -44,7 +44,8 @@ Version settings are important in several scenarios: * Adding a version of Mule or Java that is missing from your project * Selecting versions of Mule or Java that are compatible with each other -NOTE: Changing the minimum Mule version (`minMuleVersion`) manually can have serious implications. This requires a full test of your application so it works correctly with the target Mule runtime. Newer Mule runtimes turn on feature flags by default and can change behavior that was fixed in later versions. Your application can rely on behavior that was later corrected or on a previous issue. Prefer changing the Mule version through *Project Properties*, and always run full regression tests after any version change. +[NOTE] +Changing the minimum Mule version (`minMuleVersion`) manually can have serious implications. This requires a full test of your application so it works correctly with the target Mule runtime. Newer Mule runtimes turn on feature flags by default and can change behavior that was fixed in later versions. Your application can rely on behavior that was later corrected or on a previous issue. Prefer changing the Mule version through *Project Properties*, and always run full regression tests after any version change. When a Mule or Java version isn't set for a project, the IDE's canvas and notifications provide a *Set version* button that opens the *Project Properties* tab. You can also navigate directly to the *Project Properties* tab. From 8d9e4a1d36bfdb8eb4afc07f892ad625221b0d58 Mon Sep 17 00:00:00 2001 From: Cristian Date: Mon, 9 Feb 2026 22:11:13 -0300 Subject: [PATCH 3/3] W-21199055-Address-Rodrigo-feedback-CP --- modules/ROOT/pages/int-versions.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/ROOT/pages/int-versions.adoc b/modules/ROOT/pages/int-versions.adoc index d91532e83..c0c61e2b1 100644 --- a/modules/ROOT/pages/int-versions.adoc +++ b/modules/ROOT/pages/int-versions.adoc @@ -45,7 +45,7 @@ Version settings are important in several scenarios: * Selecting versions of Mule or Java that are compatible with each other [NOTE] -Changing the minimum Mule version (`minMuleVersion`) manually can have serious implications. This requires a full test of your application so it works correctly with the target Mule runtime. Newer Mule runtimes turn on feature flags by default and can change behavior that was fixed in later versions. Your application can rely on behavior that was later corrected or on a previous issue. Prefer changing the Mule version through *Project Properties*, and always run full regression tests after any version change. +Changing the minimum Mule version (`minMuleVersion`) manually can have serious implications. This requires a full test of your application so it works correctly with the target Mule runtime. Newer Mule runtimes turn on feature flags by default. See xref:mule-runtime::feature-flagging.adoc[]. This can change behavior that was fixed in later versions. Your application can rely on behavior that was later corrected or on a previous issue. Prefer changing the Mule version through *Project Properties*, and always run full regression tests after any version change. When a Mule or Java version isn't set for a project, the IDE's canvas and notifications provide a *Set version* button that opens the *Project Properties* tab. You can also navigate directly to the *Project Properties* tab.