January 2025 release
Release: 5.2.2501.1461+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.
Note
The January 2025 release is now available for developers to download and work with locally or to request deployments.
Release highlights
- You can now define a sender name in the email addressdefine a sender name in the email address values stored in the Admin Console settings.
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.
Medium risk for Spire
- Updated Spire to Node22 – Node18 is approaching end of life. Internally, the development team has moved from nvm to https://volta.sh/ and have node versions pinned in the appropriate package.json files. This provides an improved development experience as volta auto detects and installs/uses pinned node versions.
Low risk
- Fixed a console warning on LocationFinder page – Upgraded @react-google-maps/api package to v2.20.5.
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
- Added a Use Ship-to# for Payment Gateway Vault setting for the TokenEx Adyen integrationTokenEx Adyen integration, which lets the integration use the customer sequence number for an account when vaulting cards. If the customer sequence number does not exist, it uses the bill-to number instead.
- Added the ability to define a sender name in the email addressdefine a sender name in the email address values stored in the Admin Console settings.
- Updated the Stripe integration to send the IP address from the ProcessCreditCardTransactions handler to Stripe as a metadata item.
- Changed WhereContains to work the same as Where(o => list.Contains(o.Id)) for efficiency and reliability.
- Improved security in nanoid generation.
- Improved security by moving FontProcessing to ServerSide only.
- Increased the page size of the LoadVariantChildren handler in Spire to 1000.
Bug fixes
- Fixed an issue where the Customer field was not available as a column on the PunchOut Customer User Profile Map grid.
- Fixed an issue where ShipTo Lookup did not map the correct number of property values for the CustomerOrder entity.
- Fixed an issue in Spire where the public function ISpreadsheetService.PopulateStream failed to generate a CSV.
- Fixed an issue where Punchout had the wrong encoding, causing some calls to fail.
- Fixed a processing error in Spire when you used Pay by Bank with Adyen.
- Fixed a display name issue for attribute types that had a "_" value in the name.
- Fixed an issue where the canonical URL did not work correctly when it contained a special character.
- Fixed a BillToldShipTold warning that displayed when the string did not contain the character "|".
- Fixed an issue in Spire where the meta description displayed an error in code.
- Fixed an issue where the Stripe payment gateway did not populate Address Line 2 for orders.
- Fixed errors with library dependencies when you generated a PDF on the Quote Detail page and other pages.
- Fixed allowed library issues with NetCore.
Related Support Articles
None.