Release information
Adobe organizes storefront application releases into logical suite versions and follows a regular release schedule (approximately once a month). However, Adobe may release updates more frequently to deliver new features or address critical issues.
Compatibility table
The following table shows the compatibility between all of the storefront release items by suite version:
Storefront suite | 1.0.0 | |
---|---|---|
Adobe Commerce | 2.4.7 | |
Storefront Compatibility Package | 4.7.0 | |
Drop-in SDK | @dropins/tools@0.38.0 @dropins/build-tools@0.1.1 | |
Drop-in components | @dropins/storefront-cart@1.0.1 @dropins/storefront-checkout@1.0.0 @dropins/storefront-order@1.0.0 @dropins/storefront-pdp@1.0.0 @dropins/storefront-user-account@1.0.0 @dropins/storefront-user-auth@1.0.0 |
Code changes
Every release includes changes to one or more codebases described in the compatibility table. The scope of the change determines whether the MAJOR, MINOR, or PATCH number increases in the application’s version according to semantic versioning:
Given a version number MAJOR.MINOR.PATCH, increment the:
MAJOR version when you make incompatible API changes
MINOR version when you add functionality in a backward-compatible manner
PATCH version when you make backward-compatible bug fixes
Public API
To determine when we increment the MAJOR version we must define a public API. The public API for drop-in components includes the following:
Integration APIs
Integration APIs are functions that are exposed to the storefront application to integrate the drop-in components. These functions are defined in the drop-in SDK and are used by the drop-in components.
File | Function Signatures |
---|---|
@dropins/tools/fetch-graphql.js | setEndpoint setFetchGraphQlHeader removeFetchGraphQlHeader setFetchGraphQlHeaders fetchGraphQl getConfig |
@dropins/tools/event-bus.js | on emit lastPayload |
@dropins/tools/initializer.js | mountImmediately |
@dropins/tools/lib.js | debounce getFormValues getFormErrors classes deepmerge merge generateSrcset |
Slots
Slots are built-in extension points in the drop-in components to add your own UI components and functions. The following table lists the default properties and individual drop-in slots that are available:
Type | Description |
---|---|
Default properties available to all slots: | Function signatures of the following functions:prependSibling prependChild replaceWith appendChild appendSibling getSlotElement onChange |
Structure of the dictionary object | |
Individual drop-in slots | Function signatures as defined elsewhere on this site (for example, cart slots) |
Drop-in design tokens
Drop-in design tokens are defined in the drop-in SDK and are used by the drop-in components to style the storefront application.