build(deps): bump the all-dependencies group with 6 updates

[dependabot]

Bumps the all-dependencies group with 6 updates:

Package	From	To
vitepress-shopware-docs	1.1.3	1.1.4
@shopware-docs/cli	1.1.3	1.1.4
@shopware-docs/storybook	1.1.3	1.1.4
@shopware-docs/vitepress	1.1.3	1.1.4
@shopware-docs/vitest	1.1.3	1.1.4
algoliasearch	4.21.1	4.22.0

Updates vitepress-shopware-docs from 1.1.3 to 1.1.4

Updates @shopware-docs/cli from 1.1.3 to 1.1.4

Updates @shopware-docs/storybook from 1.1.3 to 1.1.4

Updates @shopware-docs/vitepress from 1.1.3 to 1.1.4

Updates @shopware-docs/vitest from 1.1.3 to 1.1.4

Updates algoliasearch from 4.21.1 to 4.22.0

Release notes

Sourced from algoliasearch's releases.

4.22.0

v4.22.0

• fix(recommend): update TrendingFacetHit facetValue type to string (#1498) (ac9d6e2), closes #1498

Why

The trending-facets API only returns type string for facetValue.

A follow-up on #1494 as other models return items/hits which are of type RecordWithObjectID

However, trending-facets model returns a list of TrendingFacetHit which (by definition) don't have an objectID property.

How

To simplify the code, we can remove the type argument TObject for trending-facets

Impact

If you're not using TypeScript or the trending-facets model, there is nothing to change. You can ignore the following.

Otherwise, you will need to remove the type argument passed to getTrendingFacets and the code goes from this:

type FacetType = {
  facetName: string;
  facetValue: string;
}
const { results } = await client.getTrendingFacets<FacetType>(/**/)

To this:

const { results } = await client.getTrendingFacets(/**/)

Changelog

Sourced from algoliasearch's changelog.

v4.22.0

• fix(recommend): update TrendingFacetHit facetValue type to string (#1498) (ac9d6e2), closes #1498

Commits

• 5a2a128 chore: release v4.22.0 (#1499)
• ac9d6e2 fix(recommend): update TrendingFacetHit facetValue type to string (#1498)
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions