Release Notes
In this section, we have summarized the changes to Umbraco Commerce released in each version. Each version is presented with a link to the Umbraco Commerce issue tracker showing a list of issues resolved in the release. We also link to the individual issues themselves from the detail.
If there are any breaking changes or other issues to be aware of when upgrading they are also noted here.
If you are upgrading to a new major version, check the breaking changes in the Version Specific Upgrade Notes article.
We've listed here all the changes going back to the launch of Umbraco Commerce in 2023. For details of releases for Vendr, refer to the Change log file on Github.
In this section, you can find the release notes for each version of Umbraco Commerce. For each major version, you can find the details about each release.
- Fixed issue with Storefront API causing value converter error due to multiple value converts for the same property editor being found. Storefront API value converters are now no longer discoverable. They are instead registered only when
AddStorefrontApi
is called on theIUmbracoCommerceBuilder
instance #429
- All items listed under 12.1.0-rc1.
- Updated
Umbraco.Commerce
package to have dependency onUmbraco.Commerce.Cms.Web.Api.Storefront
so that an explicit dependency isn't needed. - Allow overriding of
SameSite
/Path
for Umbraco Commerce cookies. - Updated product adapter to resolve product details correctly from child node variants.
- Added headless Storefont API.
- Added templating functionality to payment provider settings to allow dynamic value resolution. For example the template
{Order.OrderNumber}
would inject the order number into the given setting value. - Added
IProductSnapshotWithImage
interface to allow product snapshots to expose a product image. - Updated default order number template from
CART-{0}
toORDER-{0}
. - Updated product adapter to resolve product details correctly from child node variants.
- Allow overriding of
SameSite
/Path
for Umbraco Commerce cookies. - Updated
productSource
resolution to check for bothIPublishedContent
andIEnumerable<IPublishedContent>
as it depends on the picker used and what its return type is.
- Updated default order number template from
CART-{0}
toORDER-{0}
. - Updated product adapter to resolve product details correctly from child node variants.
Last modified 12d ago