Bump dessant/support-requests from 3 to 4

[dependabot]

Bumps dessant/support-requests from 3 to 4.

Release notes

Sourced from dessant/support-requests's releases.

v4.0.0

Learn more about this release from the changelog.

Changelog

Sourced from dessant/support-requests's changelog.

3.0.0 (2022-12-04)

⚠ BREAKING CHANGES

• the action now requires Node.js 16

Bug Fixes

• update dependencies (98a49e5)
• update docs (d40910d)

2.1.2 (2021-10-02)

2.1.1 (2021-07-09)

Bug Fixes

• update GitHub API calls (fa1e92b)

2.1.0 (2021-07-09)

Features

• default github-token to github.token (#7) (731cce0)
• document the use of personal access tokens (6ba0377)

Bug Fixes

• declare required permissions (692a08a)
• lock temporarily unlocked issues even after an error (182adbd)

2.0.1 (2021-01-01)

Bug Fixes

• update dependencies (f502ca6)

2.0.0 (2020-08-24)

⚠ BREAKING CHANGES

• The deployment method and configuration options have changed.

Features

... (truncated)

Commits

• 47d5ea1 chore(release): 4.0.0
• 4a281e9 chore: update package
• 31ecc82 chore: update docs
• 7e8888e fix: always apply close and lock reason
• cb26bc2 feat: set close reason
• 2755608 fix: retry and throttle GitHub API requests
• 1f28647 chore: migrate package to ESM
• 008bb20 fix: update dependencies
• 0199d3b chore: rename default branch
• 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 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)

Summary by Sourcery

CI:

• Update GitHub Actions workflow to use dessant/support-requests version 4.

[sourcery-ai]

Reviewer's Guide by Sourcery

This is a dependency update PR that bumps the version of dessant/support-requests GitHub Action from v3 to v4. The change is implemented through a simple version update in the workflow file.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change	Details	Files
Update GitHub Action version reference	Bump dessant/support-requests action version from v3 to v4 Update made in GitHub Actions workflow configuration	.github/workflows/support.yml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time. You can also use
  this command to specify where the summary should be inserted.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[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 generate docstrings to generate docstrings for this PR. (Experiment)
• @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.

[sourcery-ai]

We have skipped reviewing this pull request. It seems to have been created by a bot (hey, dependabot[bot]!). We assume it knows what it's doing!

[codiumai-pr-agent-free]

CI Failure Feedback 🧐

(Checks updated until commit 8f401ff)

Action: 👀 Integration Test / ubuntu-latest / node@22 / chromium

Failed stage: 👀 Run Integration Tests chromium [❌]

Failed test name: ""

Failure summary: The action failed due to a TypeScript type error during the DTS (declaration type script) build process: In the file lib/dom-export/dom-router-provider.tsx at line 10, column 30, there is a type mismatch. The type (fn: () => R) => R is not assignable to the type (fn: () => unknown) => undefined. Specifically, the type unknown is not assignable to undefined. This type error caused the DTS build to fail, resulting in the overall build process exiting with code 1.

Relevant error logs: 1: ##[group]Operating System 2: Ubuntu ... 564: packages/react-bridging build: �[32mESM�[39m �[1mdist/development/index.mjs �[22m�[32m5.04 KB�[39m 565: packages/react-bridging build: �[32mESM�[39m �[1mdist/development/chunk-JW6X4ZZR.mjs �[22m�[32m301.55 KB�[39m 566: packages/react-bridging build: �[32mESM�[39m �[1mdist/development/lib/types/route-module.mjs �[22m�[32m220.00 B�[39m 567: packages/react-bridging build: �[32mESM�[39m ⚡️ Build success in 298ms 568: packages/react-bridging build: �[34mDTS�[39m Build start 569: packages/react-bridging build: �[34mDTS�[39m Build start 570: packages/react-bridging build: �[34mDTS�[39m Build start 571: packages/react-bridging build: �[34mDTS�[39m Build start 572: packages/react-bridging build: lib/dom-export/dom-router-provider.tsx(10,30): error TS2322: Type '<R>(fn: () => R) => R' is not assignable to type '(fn: () => unknown) => undefined'. 573: packages/react-bridging build: Type 'unknown' is not assignable to type 'undefined'. 574: packages/react-bridging build: �[31mError: error occurred in dts build 575: packages/react-bridging build: at Worker.<anonymous> (/home/runner/work/react-bridging/react-bridging/node_modules/.pnpm/tsup@8.3.5_jiti@1.21.6_postcss@8.4.49_typescript@5.7.2_yaml@2.6.1/node_modules/tsup/dist/index.js:1541:26) 576: packages/react-bridging build: at Worker.emit (node:events:518:28) 577: packages/react-bridging build: at MessagePort.<anonymous> (node:internal/worker:267:53) 578: packages/react-bridging build: at [nodejs.internal.kHybridDispatch] (node:internal/event_target:816:20) 579: packages/react-bridging build: at MessagePort.<anonymous> (node:internal/per_context/messageport:23:28)�[39m 580: packages/react-bridging build: �[31mDTS�[39m �[31mBuild error�[39m 581: packages/react-bridging build: lib/dom-export/dom-router-provider.tsx(10,30): error TS2322: Type '<R>(fn: () => R) => R' is not assignable to type '(fn: () => unknown) => undefined'. 582: packages/react-bridging build: Type 'unknown' is not assignable to type 'undefined'. 583: packages/react-bridging build: lib/dom-export/dom-router-provider.tsx(10,30): error TS2322: Type '<R>(fn: () => R) => R' is not assignable to type '(fn: () => unknown) => undefined'. 584: packages/react-bridging build: Type 'unknown' is not assignable to type 'undefined'. 585: packages/react-bridging build: lib/dom-export/dom-router-provider.tsx(10,30): error TS2322: Type '<R>(fn: () => R) => R' is not assignable to type '(fn: () => unknown) => undefined'. 586: packages/react-bridging build: Type 'unknown' is not assignable to type 'undefined'. 587: packages/react-bridging build: ❌ [build] exited with exit code 1. 588: packages/react-bridging build: ❌ 1 script failed. 589: packages/react-bridging build: Failed 590: /home/runner/work/react-bridging/react-bridging/packages/react-bridging: 591: ERR_PNPM_RECURSIVE_RUN_FIRST_FAIL  react-bridging@0.1.0 build: `wireit` 592: Exit status 1 593: ELIFECYCLE  Command failed with exit code 1. 594: ELIFECYCLE  Command failed with exit code 1. 595: ##[error]Process completed with exit code 1.

---

✨ 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.