chore(deps-dev): bump sinon from 15.2.0 to 19.0.2

[dependabot]

Bumps sinon from 15.2.0 to 19.0.2.

Changelog

Sourced from sinon's changelog.

19.0.2

• 4eb4c4bc Use fix 13.0.2 version of fake-timers to get Date to pass instanceof checks (Carl-Erik Kopseng)
• a5b03db3 Add links to code that is affected by the breaking changes (Carl-Erik Kopseng)

Released by Carl-Erik Kopseng on 2024-09-13.

19.0.1

• 037ec2d2 Update migration docs (Carl-Erik Kopseng)

Released by Carl-Erik Kopseng on 2024-09-13.

19.0.0

• 3534ab4f Bump samsam and nise to latest versions (#2617) (Carl-Erik Kopseng)

  Ensures consistency and less breakage when there are "circular" dependencies.

• 912c568d upgrade fake timers and others (#2612) (Carl-Erik Kopseng)

  • Upgrade dependencies (includes breaking API in Fake Timers)
  • fake-timers: no longer creating dates using the original Date class, but a subclass (proxy)

• 9715798e Use newer @mochify/* packages (#2609) (Carl-Erik Kopseng)

  Co-authored-by: Maximilian Antoni mail@maxantoni.de

Released by Carl-Erik Kopseng on 2024-09-13.

18.0.1

Basically a patch release to update a transitive dependency in Nise.

• 03e33ec6 Pin fake-timers@11.2.2 to avoid breaking change (Carl-Erik Kopseng)
• 5a7924ad Add createStubInstance header in stubs.md (Daniel Kaplan)
• ad6804cd Bump elliptic from 6.5.5 to 6.5.7 (#2608) (dependabot[bot])
• 033287bd Bump path-to-regexp and nise (#2611) (dependabot[bot])

  Bumps path-to-regexp to 8.1.0 and updates ancestor dependency nise. These dependencies need to be updated together.

  Updates path-to-regexp from 6.2.2 to 8.1.0

  • Release notes
  • Changelog
  • Commits

... (truncated)

Commits

• 372593f 19.0.2
• 4eb4c4b Use fixed 13.0.2 version
• 968f403 Improve formatting. Add note on fix in fake-timers@13.0.2
• a5b03db Add links to code that is affected by the breaking changes
• 43e9dd1 19.0.1
• 037ec2d Update migration docs
• 62724bb 19.0.0
• dda95c2 Update lock file
• 3534ab4 Bump samsam and nise to latest versions (#2617)
• c9964eb Remove referee-sinon introduced by recent mochify merge (#2616)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by fatso83, a new releaser for sinon since your current version.

You can trigger a rebase of this PR 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 this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[github-actions]

🦙 MegaLinter status: ❌ ERROR

Descriptor	Linter	Files	Fixed	Errors	Elapsed time
✅ EDITORCONFIG	editorconfig-checker	2		0	0.03s
✅ JSON	jsonlint	2		0	0.2s
✅ JSON	npm-package-json-lint	yes		no	0.44s
✅ JSON	v8r	2		0	11.33s
✅ REPOSITORY	checkov	yes		no	11.39s
✅ REPOSITORY	gitleaks	yes		no	0.49s
✅ REPOSITORY	git_diff	yes		no	0.01s
✅ REPOSITORY	grype	yes		no	13.34s
✅ REPOSITORY	secretlint	yes		no	1.17s
✅ REPOSITORY	trivy-sbom	yes		no	1.13s
❌ SPELL	lychee	2		1	56.3s

See detailed report in MegaLinter reports
Set VALIDATE_ALL_CODEBASE: true in mega-linter.yml to validate all sources, not only the diff

MegaLinter is graciously provided by

[qodo-merge-pro]

PR-Agent was enabled for this repository. To continue using it, please link your git user with your CodiumAI identity here.

CI Failure Feedback 🧐

Action: main / auto-merge / auto-merge

Failed stage: Run dependabot/fetch-metadata@v2.2.0 [❌]

Failure summary: The action failed because of an authentication error: The dependabot/fetch-metadata@v2.2.0 action encountered an API error. The error message (401) Bad credentials indicates that the GitHub token provided is invalid or lacks the necessary permissions.

Relevant error logs: 1: ##[group]Operating System 2: Ubuntu ... 36: Uses: khulnasoft/actions/.github/workflows/job-auto-merge.yml@refs/heads/master (bb99713d9a7905b288201e2eec03cc990c09abf2) 37: Complete job name: main / auto-merge / auto-merge 38: ##[group]Run dependabot/fetch-metadata@v2.2.0 39: with: 40: github-token: *** 41: skip-commit-verification: false 42: skip-verification: false 43: ##[endgroup] 44: ##[error]Api Error: (401) Bad credentials

---

✨ CI feedback usage guide:

---

The CI feedback tool (/checks) automatically triggers when a PR has a failed check.
The tool analyzes the failed checks and provides several feedbacks:

• Failed stage
• Failed test name
• Failure summary
• Relevant error logs

In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:

/checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}"

where {repo_name} is the name of the repository, {run_number} is the run number of the failed check, and {job_number} is the job number of the failed check.

Configuration options

• enable_auto_checks_feedback - if set to true, the tool will automatically provide feedback when a check is failed. Default is true.
• excluded_checks_list - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list.
• enable_help_text - if set to true, the tool will provide a help message with the feedback. Default is true.
• persistent_comment - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true.
• final_update_message - if persistent_comment is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true.

See more information about the checks tool in the docs.

[qodo-merge-pro]

PR-Agent was enabled for this repository. To continue using it, please link your git user with your CodiumAI identity here.

CI Failure Feedback 🧐

Action: main / auto-merge / auto-merge

Failed stage: Run dependabot/fetch-metadata@v2.2.0 [❌]

Failure summary: The action failed due to an authentication error: The error message '(401) Bad credentials' indicates that the GitHub token provided is invalid or lacks the necessary permissions. This error occurred while running the 'dependabot/fetch-metadata@v2.2.0' action.

Relevant error logs: 1: ##[group]Operating System 2: Ubuntu ... 36: Uses: khulnasoft/actions/.github/workflows/job-auto-merge.yml@refs/heads/master (bb99713d9a7905b288201e2eec03cc990c09abf2) 37: Complete job name: main / auto-merge / auto-merge 38: ##[group]Run dependabot/fetch-metadata@v2.2.0 39: with: 40: github-token: *** 41: skip-commit-verification: false 42: skip-verification: false 43: ##[endgroup] 44: ##[error]Api Error: (401) Bad credentials

---

✨ CI feedback usage guide:

---

The CI feedback tool (/checks) automatically triggers when a PR has a failed check.
The tool analyzes the failed checks and provides several feedbacks:

• Failed stage
• Failed test name
• Failure summary
• Relevant error logs

In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:

/checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}"

where {repo_name} is the name of the repository, {run_number} is the run number of the failed check, and {job_number} is the job number of the failed check.

Configuration options

• enable_auto_checks_feedback - if set to true, the tool will automatically provide feedback when a check is failed. Default is true.
• excluded_checks_list - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list.
• enable_help_text - if set to true, the tool will provide a help message with the feedback. Default is true.
• persistent_comment - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true.
• final_update_message - if persistent_comment is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true.

See more information about the checks tool in the docs.

[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>, please review it.
  • 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @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.