Adobe Commerce beta releases
Beginning in June 2023 and going forward, Adobe will release public betas for patch releases (“beta releases”). Beta releases are available to all Adobe Commerce customers and partners prior to general availability (GA) and include security, compliance, performance, and high-priority quality fixes.
Release contents
Each Adobe Commerce beta release includes all the changes delivered to Adobe Commerce core code by the scheduled release date, including, but not limited to the following functional areas:
- Latest security fixes
- Performance improvements
- GraphQL improvements
- General quality bug fixes
- Community contributions
- Changes required to support compatibility with Adobe Commerce services
Naming convention and schedule
Adobe will release beta patches twice a year. The first beta patch is typically released three months after general availability of a new core application patch release.
Beta release packages have a -betaX
suffix. For example, the Adobe Commerce 2.4.7 beta release packages use the following naming convention:
2.4.7-beta1
2.4.7-beta2
See the release schedule for the list of upcoming public beta release dates.
Benefits of participating
The earlier you see the code that we are developing, the sooner you can prepare your technology and merchants for the upcoming upgrade.
While things may change, engaging with the beta releases will enable you to start understanding where in the codebase changes are happening and begin preparing in advance of the GA release date.
Beta release access
Adobe Commerce beta releases are distributed in the same way as any other Adobe Commerce patch release: as Composer metapackages on https://repo.magento.com
. The source code is avilable on GitHub.
See Composer installation quick start for more details.
Issue reporting
Adobe does not provide the standard Adobe Support Service for beta releases.
To submit feedback related to beta releases, follow our regular issue reporting flow on GitHub.
Our internal teams will monitor all critical issues reported against the latest beta release and prioritize them to be resolved prior to the GA release date.