chore(deps): bump the non-breaking-changes group with 6 updates

[dependabot]

Bumps the non-breaking-changes group with 6 updates:

Package	From	To
husky	9.1.5	9.1.6
vitest	2.0.5	2.1.0
rollup	4.21.2	4.21.3
stylelint-scss	6.5.1	6.6.0
lucide-vue-next	0.439.0	0.441.0
@tanstack/vue-query	5.55.4	5.56.2

Updates husky from 9.1.5 to 9.1.6

Release notes

Sourced from husky's releases.

v9.1.6

What's Changed

• Fix issue where example pre-commit file is generated incorrectly by @​dexmlee in typicode/husky#1519

New Contributors

• @​OlegKipchatov made their first contribution in typicode/husky#1495
• @​Byron2016 made their first contribution in typicode/husky#1499
• @​dexmlee made their first contribution in typicode/husky#1519

Full Changelog: typicode/husky@v9.1.5...v9.1.6

Commits

• a2d942a 9.1.6
• b4465ed fix: add parens around the null coalescing operator to fix issues when npm_co...
• 3b3e7f1 docs(spanish): improve spanish translation (#1504)
• dcf3aed dosc: repair support Spanish sponsors links (#1500)
• c3afd5f docs: support Spanish documentation (#1499)
• c5f4f48 docs: support Russian documentation (#1495)
• See full diff in compare view

Updates vitest from 2.0.5 to 2.1.0

Release notes

Sourced from vitest's releases.

v2.1.0

This release makes another big change to the Browser Mode by introducing locators API:

test('renders blog posts', async () => {
  const screen = page.render(<Blog />)
await expect.element(screen.getByRole('heading', { name: 'Blog' })).toBeInTheDocument()
const [firstPost] = screen.getByRole('listitem').all()
await firstPost.getByRole('button', { name: 'Delete' }).click()
expect(screen.getByRole('listitem').all()).toHaveLength(3)
})

You can use either vitest-browser-vue, vitest-browser-svelte or vitest-browser-react to render components and make assertions using locators. Locators are also available on the page object from @vitest/browser/context.

   🚀 Features

• api:
  • Make spec into a class instead of a tuple  -  by @​sheremet-va in vitest-dev/vitest#6355 (874a1)
• browser:
  • Move page.config to server.config, add more docs  -  by @​sheremet-va in vitest-dev/vitest#6252 (af2b8)
  • Make iframe scalable, improve documentation  -  by @​sheremet-va in vitest-dev/vitest#6257 (74ca1)
  • Introduce built-in locators  -  by @​sheremet-va in vitest-dev/vitest#6084 (3347f)
  • Support v8 coverage  -  by @​AriPerkkio in vitest-dev/vitest#6273 (34199)
  • Support userEvent.upload in playwright provider  -  by @​sheremet-va in vitest-dev/vitest#6442 (cf148)
  • Support --inspect  -  by @​AriPerkkio in vitest-dev/vitest#6433 (0499a)
  • Support --inspect-brk  -  by @​AriPerkkio in vitest-dev/vitest#6434 (7ab0f)
• cli:
  • Extend existing list command to output only a list of file names  -  by @​Ma-hawaj and @​sheremet-va in vitest-dev/vitest#6392 (008f0)
• coverage:
  • Add --exclude-after-remap  -  by @​AriPerkkio in vitest-dev/vitest#6309 (5932a)
• mocker:
  • Introduce @​vitest/mocker package, allow { spy: true } instead of a factory  -  by @​sheremet-va in vitest-dev/vitest#6289 (95f02)
• vitest:
  • Add "provide" option  -  by @​sheremet-va in vitest-dev/vitest#6253 (4409d)
  • Add return type and promisable mockFactory  -  by @​syi0808 and @​sheremet-va in vitest-dev/vitest#6139 (f5e0b)
  • Add vi.advanceTimersToNextFrame  -  by @​bnjm and @​sheremet-va in vitest-dev/vitest#6347 (8ff63)
  • Allow env to be stubbed to undefined  -  by @​JSanchezIO and @​sheremet-va in vitest-dev/vitest#6359 (c3b27)

   🐞 Bug Fixes

• Correctly resolve nested mocks with index file  -  by @​sheremet-va in vitest-dev/vitest#6266 (081cf)
• Don't panic when coverage.reporter is a string  -  by @​sheremet-va in vitest-dev/vitest#6267 (7b37d)
• Align RawMatcherFn type definition with Jest  -  by @​wheresrhys in vitest-dev/vitest#6351 (d09f0)
• Cjs build of vite node server  -  by @​AkaraChen in vitest-dev/vitest#6389 (12e70)
• Allow inlining vite's cached dependencies  -  by @​chriswheeldon-peakon in vitest-dev/vitest#6284 (03208)

... (truncated)

Commits

• 9f1fd18 chore: release v2.1.0
• 94a186e fix(ui): render project name consistently (#6329)
• ac698b1 fix: expect.getState().testPath always returns correct path (#6472)
• b2be23e chore: release v2.1.0-beta.7
• 0b44722 fix: ignore importer when resolving Vitest (#6469)
• 97773e2 chore: fix edge case in license files bundling (#6460)
• 7ab0f4a feat(browser): support --inspect-brk (#6434)
• 8d883cf fix(browser): exclude missed packages from optimization, print help message (...
• c321a3f chore: replace fast-glob with tinyglobby (#6274)
• 0282564 chore(deps): replace execa with tinyexec (#6454)
• Additional commits viewable in compare view

Updates rollup from 4.21.2 to 4.21.3

Release notes

Sourced from rollup's releases.

v4.21.3

4.21.3

2024-09-12

Bug Fixes

• Always respect side effects in left-hand side of optional chain (#5642)
• Update stack trace for augmented errors to not hide relevant information (#5640)

Pull Requests

• #5636: chore(deps): lock file maintenance minor/patch updates (@​renovate[bot])
• #5637: chore(deps): lock file maintenance (@​renovate[bot])
• #5640: fix: keep the message of stack up-to-date (@​TrickyPi)
• #5642: fix: include left-side effect of optional chaining in the end of hasEffectsAsChainElement (@​TrickyPi)

Changelog

Sourced from rollup's changelog.

4.21.3

2024-09-12

Bug Fixes

• Always respect side effects in left-hand side of optional chain (#5642)
• Update stack trace for augmented errors to not hide relevant information (#5640)

Pull Requests

• #5636: chore(deps): lock file maintenance minor/patch updates (@​renovate[bot])
• #5637: chore(deps): lock file maintenance (@​renovate[bot])
• #5640: fix: keep the message of stack up-to-date (@​TrickyPi)
• #5642: fix: include left-side effect of optional chaining in the end of hasEffectsAsChainElement (@​TrickyPi)

Commits

• 9f5a735 4.21.3
• bfefc79 fix: include left-side effect of optional chaining in the end of hasEffectsAs...
• fc240ed fix: keep the message of stack up-to-date (#5640)
• 766dbf9 chore(deps): lock file maintenance (#5637)
• 9124ebc chore(deps): lock file maintenance minor/patch updates (#5636)
• See full diff in compare view

Updates stylelint-scss from 6.5.1 to 6.6.0

Release notes

Sourced from stylelint-scss's releases.

6.6.0

• Added: declaration-property-value-no-unknown: add support for first-class operators (#1042).
• Added: declaration-property-value-no-unknown: add support SCSS variables as arguments in nested functions (#1042).

Full Changelog: stylelint-scss/stylelint-scss@v6.5.1...v6.6.0

Changelog

Sourced from stylelint-scss's changelog.

6.6.0

• Added: declaration-property-value-no-unknown: add support for first-class operators (#1042).
• Added: declaration-property-value-no-unknown: add support SCSS variables as arguments in nested functions (#1042).

Full Changelog: stylelint-scss/stylelint-scss@v6.5.1...v6.6.0

Commits

• 56c2f18 6.6.0
• 7fe6e01 Prepare version 6.6.0
• f8549ca Fix false positives in declaration-property-value-no-unknown for dollar var...
• 615ce4c build(deps-dev): bump postcss from 8.4.44 to 8.4.45 (#1050)
• 11b9033 build(deps-dev): bump stylelint from 16.8.1 to 16.9.0 (#1048)
• ccddc84 build(deps): bump postcss-selector-parser from 6.1.1 to 6.1.2 (#1046)
• c95a1ee build(deps-dev): bump husky from 9.1.4 to 9.1.5 (#1047)
• f2dfee3 build(deps): bump postcss-resolve-nested-selector from 0.1.4 to 0.1.6 (#1045)
• See full diff in compare view

Updates lucide-vue-next from 0.439.0 to 0.441.0

Release notes

Sourced from lucide-vue-next's releases.

New icons 0.441.0

New icons 🎨

• clock-alert (#2401) by @​jguddas

New icons 0.440.0

New icons 🎨

• headphone-off (#2445) by @​Need-an-AwP

Modified Icons 🔨

• book-open-check (#2358) by @​jguddas
• book-open-text (#2358) by @​jguddas
• book-open (#2358) by @​jguddas
• caravan (#2423) by @​jguddas

Commits

• See full diff in compare view

Updates @tanstack/vue-query from 5.55.4 to 5.56.2

Release notes

Sourced from @​tanstack/vue-query's releases.

v5.56.2

Version 5.56.2 - 9/12/24, 6:05 PM

Changes

Fix

• core: make sure infiniteQuery always fetches the first page (#8051) (7624785) by Dominik Dorfmeister

Packages

• @​tanstack/query-core@​5.56.2
• @​tanstack/query-broadcast-client-experimental@​5.56.2
• @​tanstack/query-persist-client-core@​5.56.2
• @​tanstack/query-sync-storage-persister@​5.56.2
• @​tanstack/react-query@​5.56.2
• @​tanstack/react-query-devtools@​5.56.2
• @​tanstack/react-query-persist-client@​5.56.2
• @​tanstack/react-query-next-experimental@​5.56.2
• @​tanstack/solid-query@​5.56.2
• @​tanstack/solid-query-devtools@​5.56.2
• @​tanstack/solid-query-persist-client@​5.56.2
• @​tanstack/svelte-query@​5.56.2
• @​tanstack/svelte-query-devtools@​5.56.2
• @​tanstack/svelte-query-persist-client@​5.56.2
• @​tanstack/vue-query@​5.56.2
• @​tanstack/vue-query-devtools@​5.56.2
• @​tanstack/angular-query-experimental@​5.56.2
• @​tanstack/query-async-storage-persister@​5.56.2
• @​tanstack/angular-query-devtools-experimental@​5.56.2

v5.56.1

Version 5.56.1 - 9/12/24, 2:38 PM

Changes

Fix

• core: retry for infinite queries (issue #8046) (#8049) (a106d63) by EL AYADI Mohamed

Chore

• trigger release (6a17069) by Dominik Dorfmeister

Packages

• @​tanstack/eslint-plugin-query@​5.56.1
• @​tanstack/query-async-storage-persister@​5.56.1
• @​tanstack/query-broadcast-client-experimental@​5.56.1
• @​tanstack/query-core@​5.56.1

... (truncated)

Commits

• 763abd1 release: v5.56.2
• 666c8b2 release: v5.56.1
• d29c37a release: v5.56.0
• 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

[changeset-bot]

⚠️ No Changeset found

Latest commit: cc9ab7b

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.