Shoplazza vs Virto Commerce

Virto Commerce is publishing constantly and across parallel branches: 3.1053 through 3.1056 on the current line, plus backports onto 3.1039.x and 3.1007.x for customers pinned to older platforms. The recent content is a locked-down admin surface, an API that now returns a login redirect instead of a bare 401, a settings ValueType mismatch that was throwing 500s, and cache-accessor and contention fixes underneath.

Two things are happening at once. The visible one is release hygiene: every fix is fanned out across supported branches within hours, which is what a platform with long-lived enterprise deployments has to do, and which makes the changelog look busier than the underlying change count. The structural one is that the platform keeps shedding built-in subsystems into installable modules — background job handling was pulled out of the core into its own module rather than remaining a platform dependency.

Expect the multi-branch backport pattern to continue on every fix, and further platform subsystems to follow background jobs out of the core into optional modules that installs opt into.