The Autodiscovery element no longer appears in the Add Component panel.
|
|
Users now receive a notification after successful deployment to CloudHub as expected.
|
|
DataWeave output metadata is now correct in component fields.
|
|
The canvas now correctly reflects unsaved changes.
|
|
CloudHub redeployment no longer fails intermittently.
|
|
The Transformation Builder window for DataWeave no longer shows an error in the input sample on Windows systems.
|
|
The flow configuration UI attribute for enabling default events is now correctly written in the XML file.
|
|
The configuration UI no longer shows a default value for data types when no default value exists in the metadata.
|
|
Errors updating XML no longer occur on the canvas when updating auto closed tags.
|
|
Editing metadata in the Transform Message component now works correctly if the source is a DataWeave file.
|
|
The M2_REPO variable is now used to populate the repository at startup.
|
|
The debugger now correctly pauses in the main flow and sub-flow after using Step into.
|
|
Toggling between INLINE or Bean mode to None now works correctly in the configuration panel.
|
|
You can now input text for Operations in MuleSoft Vectors Connector as expected.
|
|
Validation now shows errors as expected for missing fields in the Database component.
|
|
The debugger now shows the breakpoint information as expected if Step into is used on a flow reference pointing to a flow in the configuration of a sub-folder.
|
|
Unauthorized errors no longer occur when the token expires.
|
|
A2A Connector configurations now appear in version 0.4.0-BETA as expected.
|
|
If deployment to CloudHub 2.0 fails, the user now gets an error notification.
|
|
Transformation Builder no longer closes unexpectedly on Windows systems when pressing Ctrl+Backspace.
|
|
Error messages no longer repeatedly pop up for the same error during dependency resolution.
|
|
A path traversal vulnerability in MuleSoft MCP Server tools is now fixed.
|
|
Intermittent corruption of the JDK installation no longer occurs.
|
|
A server-side template injection vulnerability in MCP flow generation tools is now fixed.
|
|
The Dev Agent web fetch tool timeout is increased from 10 to 30 seconds to support slow-loading URLs.
|
|
Expression Builder no longer breaks or displays incorrectly if the DataWeave transformation contains a long script.
|
|
The configuration UI in the Java module now successfully loads the Method field values.
|
|
Misleading stack traces from the Design Service logs that appeared when loading custom connectors are removed.
|
|
The HTTP Listener component now secures the password during TLS setup as expected.
|
|
The Anypoint Code Builder Integration Extension now uses the correct version of org.mule.weave dependencies instead of using the 2.6.1. version.
|
|
The Anypoint Code Builder Platform Extension version 5.9.7 no longer breaks in Windows systems.
|
|
The Expression Builder gear icon is now clickable as expected.
|
|
The Audience field in the MCP tool listener configuration no longer intermittently fails to display.
|
|
The MCP configuration reference field in the Inference Connector can now be edited as expected.
|
|
The internal platform jar socket is now restricted to listening on localhost only, mitigating a potential Remote Code Execution (RCE) vulnerability.
|
|
Object group element attributes now update correctly in the UI, and inconsistent behavior related to empty element deletion in the Transform script field no longer occurs.
|
|
Custom metadata now shows as expected in the Output column of the mapping window for transform components.
|
|
SAP Connector test connection no longer fails.
|
|
The scaffolding process no longer fails when the project ID used for scaffolding doesn’t match the project ID that was created.
|
|
Projects that are inherited from a Parent POM that use Maven’s CI-friendly version properties no longer incorrectly report that the parent POM can’t be found.
|
|
The Connectors tab in Project Properties no longer fails to load when an incompatible connector version causes the Mule framework introspection to fail.
|
|
The code editor of a component is now resizable and shows line numbers.
|
|
The drag and drop action for simple Transform components no longer breaks the canvas view and flow XML on Windows systems.
|
|
The MuleSoft Dev Agent stream no longer intermittently throws an incorrect ValidationException error embedded within stream chunks.
|
|
MuleSoft Dev Agent no longer fails due to streaming errors or server timeouts during operations.
|
|
MuleSoft Dev Agent no longer experiences a five-second delay before making the first API call after being opened.
|
|
The Map with AI feature in Transformation Builder now correctly displays user access errors when they occur.
|
|
The Edit Sample Data File icon is no longer disabled in the Map with AI feature in Transformation Builder. Also, the default call when opening the Transform UI is removed, and the UI now shows a message instead of a spinning icon when the GenAI API call fails.
|
|
Anypoint Code Builder no longer fails to render all configuration parameters, such as the HTTP Requestor parameter, for the RosettaNet Connector in the Configuration UI.
|
|
Anypoint Code Builder no longer displays an incorrect compatibility error message when a project dependency is missing in the current Exchange environment.
|
|
The Import global element now recognizes flows defined within the imported plugin as expected.
|
|
The Visual Designer no longer fails to show and recognize shared configuration components when they’re inherited from a Parent POM.
|
|
Keyboard shortcuts, such as Command+C and Command+V, now work as expected when selecting and editing text in the DataWeave Editor.
|
|