Merge pull request #581 from mulesoft/W-21199055-Create-MinMuleRuntimeVersion-note-CP

W-21199055-Create-MinMuleRuntimeVersion-note-CP

Author: Crispy-Salesforce

modules/ROOT/pages/int-versions.adoc

@@ -44,6 +44,9 @@ 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. 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.