June 2025 release
10 min
Release: 5.2.2506.1899+sts
The following is a list of the release's bug fixes and enhancements. Some bug fixes may address existing support articles. A comprehensive list is at the bottom of this page.
The June 2025 release is now available for developers to download and work with locally or to request deployments.
Release highlights
- Commerce Search v3 (beta) – Commerce Search v3 for Optimizely Configured Commerce introduces advanced search technologies tailored for B2B ecommerce platforms. It offers fast, relevant search results powered by AI and machine learning, improving user intent understanding and product ranking. See Commerce Search v3 overviewCommerce Search v3 overview for information.
- Enhanced search accuracy for higher conversion.
- Semantic and conversational search for natural interactions.
- Dynamic filtering for relevant product context.
- Seamless integration with Optimizely products.
- Improved customer experience.
- Fully managed infrastructure for scalability as the business grows.
Breaking changes
Binary breaking changes do not necessarily require code changes but rather just a recompilation of the project. This section describes breaking changes to method signatures or method behaviors in Optimizely Configured Commerce.
High risk
- Upgraded React NPM Packages – React has been upgraded to version 19.1.0. This likely requires updates to any custom widgets and components. Notable changes include but are not limited to:
- Using the PropsWithChildren type to let TypeScript if the children prop is needed.
- The use of React's findDOMNode is no longer supported. You must remove or replace any third-party NPM libraries that rely on this function.
- React.defaultProps is no longer available for functional components. You should define default prop values by JavaScript's default parameter initialization instead.
- Drag and drop functionality used to define a custom sort order in Wishlists now uses the dnd-kit/sortable NPM package instead of react-sortable-hoc.
Medium risk
- Refactored useGetLinks to appropriately call dispatch and memoize results – The useGetLinks selector has been refactored to appropriately handle loading categories and to memoize the results. This should resolve the flood of redux warning messages appearing in the browser console. The function's return signature has been updated. The result is now an object containing two properties. The links property contains the values that the function originally returned. The hasMissingCategories property is a boolean that indicates if some necessary categories have not yet been loaded.
- Updated the URL for the WIS REST API– The initial URL for the WIS REST API api/internal/integration is passed by the Admin.Api container. This was changed to integration/api, which should be handled by the integration container. WIS will stop working through REST API and fall back to WCF-based communication until you update to the latest WIS version.
Important
Optimizely recommends that you update WIS sooner rather than later.
Low risk
- Upgraded TokenEx Integration to Transparent Gateway API v2 – TokenEx is transitioning from Transparent Gateway API v1 to v2, and the current integration must be updated to maintain compatibility. The current Transparent Gateway API v1 is now in break/fix mode only and will be deprecated. This change obsoleted a method and added a new method to the non-extensible interface ITokenExUtilities.
- Added the ExcludeAttributes property to prevent loading attributes for wishlist lines – When you load wishlist lines, Configured Commerce sets it to true in CreateGetWishListLineResults.
Partners/Developers: At the bottom of this page, you can view a cumulative list of breaking changes, including Spire breaking changes. The spreadsheet has two tabs: one for cumulative breaking changes and one for Spire breaking changes.
Database changes and updates
No significant changes.
Library changes and updates
No significant changes.
Enhancements
- (Beta) Added Commerce Search v3 with advanced search technologies tailored for B2B ecommerce platforms. It offers fast, relevant search results powered by AI and machine learning, improving user intent understanding and product ranking. See Commerce Search v3 overviewCommerce Search v3 overview for information.
- Added the ability to see the outcome of AddPaymentProfile. A successful save of a payment profile logs a debug message describing the event. A failure logs a warning with as much information as possible.
- Upgraded the TokenEx integration to Transparent Gateway API v2 to ensure continued functionality and security.
- Improved performance for the Wishlist API.
- Improved performance of ProductUtilities.IsVisible.
- Improved the translation performance of GetProductDataUtilities.PopulateAttributes.
- Removed byte-order mark (BOM) from 1200_CreateResponse.
- Updated the login lockout message to show Account is locked out message for correct username and password combinations and Invalid Username/Password combination message if the password is incorrect.
- Updated the URL for Netcore's REST API integration. Optimizely recommends updating WIS.
Bug fixes
- Fixed an issue with storefront links where the GTM ID incorrectly had single quotes around its valueFixed an issue with storefront links where the GTM ID incorrectly had single quotes around its value.
- Fixed an issue in Spire where the checkout page did not refresh after a 3DS failure, which caused some issues with the Spreedly payment process.
- Fixed SQL errors that occurred in non-HTTP workflows.
- Fixed an issue in Spire where the date picker showed current year dates when you configured a custom budget for a future year.
- Fixed an issue where the Admin login form/API did not enforce the maximum password length requirement of 100 characters.
- Fixed an issue where Payment Service gave an error that it was not enabled.
- Fixed an issue where you could not select and assign VMI users.
- Fixed an issue where the Console Users page displayed the incorrect language under the Default Admin Console Language filter.
- Fixed an issue in Spire where passwords containing underscores were not recognized as having non-alphanumeric characters, causing validation errors.
- Fixed an issue where orderLine.Description in order confirmation emails used the default system language instead of the user's selected language.
- Fixed an issue in Spire where your changes to the Assign Ship To Address modal were not saved when editing a user in the user administration section.
- Fixed an issue where you were unable to export CMS content from a sandbox using the Import/Export link from CMS settings.
- Fixed an issue with quote checkout.
Related Support Articles
- SA1691141-Incorrect format of GTM link on StoreFront2ZH3GGSA1691141-Incorrect format of GTM link on StoreFront2ZH3GG