Product Updates

Changes to Magento

Everything we have shipped to Magento, release by release.

8 changes
3 releases
since October 2026

Latest release

25 October 2026

Release notes · 4 changes

New features: 3
Improvements: 1

Highlights

New

Varnish full-page cache for Magento on CoreStack and CoreCluster

Magento 2 sites on CoreStack and CoreCluster can now serve pages from Varnish. Switch it on or off, choose its version, purge it by URL, tag or pattern, add your own VCL with validation, history and revert, and follow its hit ratio in the Corefinity control panel, the API and the MCP tools; deployments purge it for you.

New

Several sending domains per site

A Magento site can send each store's mail through its own verified sending domain, chosen by the From address.

New

New Magento 2 sites start with Varnish switched on

New Magento 2 sites on CoreStack and CoreCluster now start with Varnish full-page cache switched on, and new environments follow their site's Varnish setting. You can switch it off or choose its version when you create the site, or at any time afterwards, in the Corefinity control panel, the API or the MCP tools.

Improved

Magento sites with several stores can serve each store on its own address

A Magento 2 site that runs more than one store can now have each store answer on its own address, a platform address or a domain of its own, with the right store shown on each. Ask support to set it up for your site.

Earlier releases

19 October 2026

Release notes · 1 change

1 fixed

Fixed

Laravel and Magento sites show their real database name

A Laravel or Magento 2 site's database details now show application, the name of the database the site really uses. They showed wordpress by mistake.

12 October 2026

Release notes · 3 changes

3 fixed

Fixed

Magento 2 git deployments now build correctly

When a Magento 2 site deploys from git, its code is now compiled with the site's own PHP version before it goes live, using your Magento Marketplace keys from Company settings when the project needs them. Before this, these deployments stopped at the build step.

Fixed

A retried Magento 2 git deployment reuses its build

Retrying a Magento 2 git deployment whose build had already finished now deploys that build again instead of failing at the build step. A step that fails without a message now says when the connection to the site was lost.

Fixed

Copying a Magento 2 environment's files and database no longer fails

Copying a Magento 2 environment's files and database into another environment finished copying and then failed with "The copy finished but the target could not be adjusted". The target's own database password is now set first, so its URLs and settings are updated and the copy completes.

{ Contact us }

Let's Talk

Tell us about your platform and goals. Our engineers will help you find the right performance setup, no sales pressure, just expert advice.