Skip to content

chore: next version release - #2605

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
changeset-release/main
Open

chore: next version release#2605
github-actions[bot] wants to merge 1 commit into
mainfrom
changeset-release/main

Conversation

@github-actions

@github-actions github-actions Bot commented Aug 4, 2026

Copy link
Copy Markdown
Contributor

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@shopware/cms-base-layer@4.0.0

Major Changes

  • #2609 2dc86da Thanks @mkucmus! - Make the package a plain Nuxt layer.

    Breaking: the package now declares an exports map, so only the layer entry point
    is importable. Deep imports such as
    @shopware/cms-base-layer/app/components/SwProductCard.vue no longer resolve. Use the
    auto-registered global components instead, which is what extending the layer gives you.

    Breaking: the leftover Nuxt module is gone, so index.cjs and the dist build are
    no longer published. The module registered a component folder that moved to app/ a
    while ago, so it could not work any more. Consume this package with extends, which
    resolves nuxt.config.ts:

    export default defineNuxtConfig({
      extends: ["@shopware/cms-base-layer"],
    });

    Other changes:

    • Dropped the build and dev scripts and the unbuild dev dependency. There is
      nothing left to bundle.
    • Fixed files. It listed helpers and app.config.ts, which do not exist at the
      package root, and shipped the dead dist and index.cjs.
    • Deleted components.d.ts. It typed two components at paths that moved to
      app/components/public/cms/, and no tsconfig referenced the file.
    • Removed two vitest aliases that pointed at files which do not exist.
    • Removed the check-colors script. It read uno.config.ts from this package, which
      moved to @shopware/unocss-design-tokens-layer, so it always found zero colors. It
      also relied on tsx without declaring it.

Minor Changes

  • #2574 2ddf156 Thanks @mkucmus! - SwProductListingFilters and SwProductListingFiltersHorizontal render a new SwFilterCategories checkbox filter when the listing response contains the category aggregations from getCategoryFilterAggregations(). The selection is kept in the categories URL param and applied as a criteria post-filter. Both are search listings only (listing-type="productSearchListing"); on any other listing the category filter is not rendered, because the selection would neither reach the URL nor the criteria. Listings without these aggregations are unaffected.

Patch Changes

  • #2606 1c9a604 Thanks @mkucmus! - Stop leaking internal types into the layer's public type surface.

    • index.d.ts now only augments the app config. It no longer re-exports @shopware/composables and ./.nuxt/imports.
    • The #imports shim moved to a private types/imports.d.ts, which is not published.
    • app.config exports a plain object with satisfies AppConfigInput instead of calling defineAppConfig. No runtime change.

    This fixes Cannot find name 'ref' and similar errors in the shared and node contexts when a project uses the Nuxt 4 project-references tsconfig.json.

  • #2601 e64d2f9 Thanks @mdanilowicz! - Typography for CMS-authored HTML is now scoped to a cms-element-text class and ships from the layer as app/assets/css/rich-text.css, with overflow guards for long strings, media, pre and tables. Headings and lists in your own markup that had no explicit size or list-* class were relying on the removed global rules and will change.

  • Updated dependencies [2ddf156, 204c8f4]:

    • @shopware/helpers@1.8.0
    • @shopware/composables@1.12.2

@shopware/helpers@1.8.0

Minor Changes

  • #2574 2ddf156 Thanks @mkucmus! - Add getCategoryFilterAggregations() and getCategoryFilterPostFilter() to request category aggregations for product listings and filter by category without reducing the aggregations. excludeRootCategory() drops the sales channel entry point from the category entities, and the CATEGORY_AGGREGATION_NAME / CATEGORY_COUNTS_AGGREGATION_NAME / CATEGORY_PARENTS_AGGREGATION_NAME constants are exported for consumers that build the aggregations themselves.

    getListingFilters (@beta) merges the categories and categories-counts response aggregations into a single categories filter with a product count per category. This changes the shape of that filter for listings that already requested a categories aggregation: the entities are sorted by count (highest first) instead of keeping the response order, each entity gains a count, the filter no longer carries the aggregation's apiAlias, and categories-counts is no longer returned as a filter of its own.

Patch Changes

  • #2598 204c8f4 Thanks @dependabot! - Fix Nuxt plugin injection typing for Nuxt 4.5 and maintenance mode error handling.

@shopware/composables@1.12.2

Patch Changes

@shopware/nuxt-module@1.5.2

Patch Changes

  • #2598 204c8f4 Thanks @dependabot! - Fix Nuxt plugin injection typing for Nuxt 4.5 and maintenance mode error handling.

  • Updated dependencies [2ddf156, 204c8f4]:

    • @shopware/helpers@1.8.0
    • @shopware/composables@1.12.2

@shopware/unocss-design-tokens-layer@1.0.2

Patch Changes

  • #2632 9274aa8 Thanks @mkucmus! - Load presetWind3 from @unocss/preset-wind3 instead of the unocss barrel in
    uno.runtime.config.ts.

    That file is imported by a client plugin, and the barrel statically re-exports
    @unocss/transformer-attributify-jsx. That transformer depends on oxc-parser, whose
    browser entry imports @oxc-parser/binding-wasm32-wasi. The binding is not present in a
    production install, so the client bundle failed to build:

    [vite]: Rolldown failed to resolve import "@oxc-parser/binding-wasm32-wasi"
    from "oxc-parser/src-js/wasm.js"
    

    The parser never runs in the browser. Importing the preset directly keeps it out of the
    client graph and also stops a 1.4 MB .wasm file and its worker from being emitted into
    the public bundle.

@vercel

vercel Bot commented Aug 4, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
frontends-starter-template-extended Ready Ready Preview Aug 17, 2026 12:43pm
frontends-vue-starter-template Ready Ready Preview Aug 17, 2026 12:43pm

Request Review

@github-actions
github-actions Bot force-pushed the changeset-release/main branch from d1f413b to 7e05ad0 Compare August 5, 2026 07:52
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 7e05ad0 to d682c23 Compare August 5, 2026 19:24
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from d682c23 to 927a663 Compare August 7, 2026 11:59
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 927a663 to ec2ce0a Compare August 7, 2026 16:05
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from ec2ce0a to 5a55e6d Compare August 10, 2026 08:49
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 5a55e6d to 678cc4b Compare August 10, 2026 09:21
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 678cc4b to e9815ba Compare August 10, 2026 09:23
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from dd6b189 to 7ba146f Compare August 12, 2026 11:25
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 7ba146f to a35482c Compare August 17, 2026 08:29
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from a35482c to 0e7348c Compare August 17, 2026 09:03
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 0e7348c to 003fb91 Compare August 17, 2026 09:48
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 003fb91 to aa4af44 Compare August 17, 2026 09:56
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from aa4af44 to 601da3a Compare August 17, 2026 11:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants