Releases · shopware/shopware

30 Jun 12:15

github-actions

v6.7.0.1

911fdd2

Release v6.7.0.1 Latest

Latest

See the UPGRADE.md for all important technical changes.

Assets 2

17 Jun 07:58

alvarothomas

v6.7.0.0

aabbca9

Shopware 6.7.0.0

This major release introduces significant technical improvements, cleanup of deprecated features, upgraded accessibility changes and impactful changes for long-term platform stability. After a RC validation period in different phases, the 6.7 release is now production-ready for self-hosted environments.

Highlights

Vue 3 is now fully supported in the administration. The compatibility layer has been removed, and Pinia replaces Vuex for state management.
Webpack has been replaced with Vite for the administration build process, improving performance and DX.
Storefront and Admin templates have been migrated to the Meteor Component Library. Several legacy components have been deprecated or removed.
The cache system has been reworked. Store-API route caching has been removed, and ESI was introduced for more precise cache control.
Native type declarations have been added to PHP class properties across the platform.
Multiple core libraries were upgraded: DBAL 4.x, PHPUnit 11.x, Dompdf 3.x, oauth2-server 9.x.
The OAuth token request flow is now spec-compliant. The /api/oauth/authorize endpoint has been removed.
Accessibility improvements have been made across the admin UI in preparation for the European Accessibility Act (EAA).

Deprecation Cleanup

6.7 finalizes the deprecation removals that were scheduled during the 6.6 lifecycle. Please refer to the Upgrade Guide for detailed migration instructions.

Upgrade Considerations

Plugin and app developers should test compatibility, particularly with the Vue 3 and Vite changes.
Private apps and themes may require additional review due to internal API and caching adjustments.
Redis configuration and Varnish now rely on updated modules. See the hosting section in the upgrade guide.

Additional Resources

Upgrade Guide

Developer Changelog

The changes introduced between RC5 and the final release were limited to bug fixes and minor adjustments. No additional breaking changes were introduced after RC5.

Assets 2

10 Jun 08:38

github-actions

v6.6.10.5

c6c86bb

Release v6.6.10.5

See the UPGRADE.md for all important technical changes.

Contributors

wrongspot, OliverSkroblin, and 4 other contributors

Assets 2

28 May 13:53

github-actions

v6.7.0.0-rc5

c4fafcb

Release v6.7.0.0-rc5

See the UPGRADE.md for all important technical changes.

Contributors

amenk and aragon999

Assets 2

15 May 11:54

github-actions

v6.7.0.0-rc4

d1ba176

Release v6.7.0.0-rc4

Notable Changes

Mitigate Meteor components migration with deprecated components

To support extension developers and ensure compatibility between Shopware 6.6 and Shopware 6.7, a new prop called deprecated has been added to Shopware components.

Prop Name: deprecated
Default Value: false (uses the new Meteor Components by default)
Purpose:
- When deprecated is set to true, the component will render the old (deprecated) version instead of the new Meteor Component.
- This allows extension developers to maintain a single codebase compatible with both Shopware 6.6 and 6.7 without being forced to immediately migrate to Meteor Components.

Example:

<!-- Uses mt-button in 6.7 and sw-button-deprecated in 6.6 -->
<template>
  <sw-button />
</template>


<!-- Uses sw-button-deprecated in 6.6 and 6.7 -->
<template>
  <sw-button deprecated />
</template>

Improve extensibility of header and footer ESI templates

With this change it is possible to add query parameters to the header/footer ESI requests.
This could be used to customize the header/footer templates.

Extending the src/Storefront/Resources/views/storefront/base.html.twig file:

{% sw_extends '@Storefront/storefront/base.html.twig' %}
{% block base_esi_header %}
    {% set headerParameters = headerParameters|merge({ 'vendorPrefixPluginName': { 'activeRoute': activeRoute } }) %}
    {{ parent() }}
{% endblock %}

Within a plugin, you can also use the Shopware\Storefront\Event\StorefrontRenderEvent

class StorefrontSubscriber
{
    public function __invoke(StorefrontRenderEvent $event): void
    {
        if ($event->getRequest()->attributes->get('_route') !== 'frontend.header') {
            return;
        }

        $headerParameters = $event->getParameter('headerParameters') ?? [];
        $headerParameters['vendorPrefixPluginName']['salesChannelId'] = $event->getSalesChannelContext()->getSalesChannelId();

        $event->setParameter('headerParameters', $headerParameters);
    }
}

After that you can use this data to customize the header template:

{% sw_extends '@Storefront/storefront/layout/header.html.twig' %}
{% block header %}
    {{ dump(headerParameters.vendorPrefixPluginName.activeRoute) }}
    {{ dump(headerParameters.vendorPrefixPluginName.salesChannelId) }}
    {{ parent() }}
{% endblock %}