March 2025 release

  • Updated

Release: 5.2.2503.1551+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 March 2025 release is now available for developers to download and work with locally or to request deployments.

Release highlights

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.

Low risk

  • Removed Prometheus from the codebase – The Prometheus.NetStandard nuget package has been removed from the allowed libraries list.

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

Spire enhancements

  • Optimized 404 errors in Spire to not render a page.

Other enhancements

  • Added the ability to auto-map fields for job definition steps using Opti AI.
  • Improved performance of VMI bin counts.
  • Added webview authorization for the Mobile App by signing the user in using cookies so that webview stays signed in based on the user activity and sliding expiration.
  • Updated the job notification and link conditions to Success, Warning, Error, and Failure.
  • Added settings in the Admin Console to disable local login for users when you have single sign-on (SSO) enabled.
  • Updated the VantivExpress live URLs.
  • Added support for Adyen Vaulting in Payment Service.
  • Added the ability for users to enter a CVV when they select a saved payment method during checkout.
  • Added product translations to the Export Product Feed.
  • Added a setting under Administration > Settings > Punchout to choose what text data type to use for status responses. If Yes, the status response format is <Status code="200" text="OK"/> (cXML format). If No (default), the status response format is <Status code="200" message="OK"/>.
  • Implemented a small performance improvement by cutting the PipeAssemblyFactory overhead by 50%. This is used by all IPipe-based workflows.
  • Improved the memory efficiency of text strings stored in the memory cache, key/value lists in the entity cache, and URL redirects.
  • Improved large cart base code performance by up to 15% by preventing repeated-per-cart-line retrieval of product settings.
  • Improved large cart performance by up to 5% by removing ObjectToObjectMapper from GetCartLineMapper. This affects Cart V1 and Cart V2.
  • Added direct references to System.Net.Http to prevent errors when you update VisualStudio. See the notice for details.
  • Removed Prometheus as the code was no longer being used.

Bug fixes

  • Fixed an issue in Spire where the description field was missing from the product structured data on the product detail page.
  • Fixed an issue where filtering a large number of website users by role in the Admin Console caused an error in the application logs.
  • Fixed an issue where cached values were shared across websites instead of differentiating between default salespersons.
  • Fixed an issue in Spire where the fulfillment method for a customer's cart changed back to Pickup after they logged in.
  • Fixed an issue in Spire where the product detail page loaded twice with Server-Side Rendering.
  • Fixed an unhandled error when you added a CRON Expression column to the Job Definitions table.
  • Fixed an issue in Spire where HTML attributes were removed from Rich Text and Code Snippet widgets.
  • Fixed an issue where a large number of "Value cannot be null" errors displayed in the application log.
  • Fixed allowed library issues with NetCore.

Related Support Articles

Configured Commerce REST APIs

Cumulative breaking changes spreadsheet