Bump @todesktop/cli from 1.10.5 to 1.11.1 in /packages/scalar-app in the todesktop-dependency-update group across 1 directory

[dependabot]

Bumps the todesktop-dependency-update group with 1 update in the /packages/scalar-app directory: @todesktop/cli.

Updates @todesktop/cli from 1.10.5 to 1.11.1

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

Summary by Sourcery

Build:

• Update @todesktop/cli dependency from version 1.10.5 to 1.11.1 in the /packages/scalar-app directory.

[sourcery-ai]

Reviewer's Guide by Sourcery

This is a dependency update PR that bumps the version of @todesktop/cli from 1.10.5 to 1.11.1 in the scalar-app package. The change is implemented through a simple version update in the package.json file.

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

File-Level Changes

Change	Details	Files
Update @todesktop/cli development dependency version	Bump version from ^1.10.5 to ^1.11.1 Update made in devDependencies section	packages/scalar-app/package.json

---

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. (Beta)
• @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. Here's why:

• It seems to have been created by a bot (hey, dependabot[bot]!). We assume it knows what it's doing!
• We don't review packaging changes - Let us know if you'd like us to change this.

[codiumai-pr-agent-free]

CI Failure Feedback 🧐

(Checks updated until commit 89a6e62)

Action: validate (20)

Failed stage: Install dependencies [❌]

Failure summary: The action failed because the pnpm-lock.yaml file is out of sync with packages/scalar-app/package.json. Specifically: The package @todesktop/cli version in package.json (^1.11.1) doesn't match the version in the lockfile (^1.10.5) The action was running with --frozen-lockfile flag (default in CI environments) To fix this, the lockfile needs to be updated locally by running pnpm install and committing the changes

Relevant error logs: 1: ##[group]Operating System 2: Ubuntu ... 29: Statuses: read 30: ##[endgroup] 31: Secret source: Dependabot 32: Prepare workflow directory 33: Prepare all required actions 34: Getting action download info 35: Download action repository 'actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683' (SHA:11bd71901bbe5b1630ceea73d27597364c9af683) 36: Download action repository 'pnpm/action-setup@fe02b34f77f8bc703788d5817da081398fad5dd2' (SHA:fe02b34f77f8bc703788d5817da081398fad5dd2) 37: ##[warning]Failed to download action 'https://api.github.com/repos/pnpm/action-setup/tarball/fe02b34f77f8bc703788d5817da081398fad5dd2'. Error: The request was canceled due to the configured HttpClient.Timeout of 100 seconds elapsing. 38: ##[warning]Back off 17.375 seconds before retry. 39: ##[warning]Failed to download action 'https://api.github.com/repos/pnpm/action-setup/tarball/fe02b34f77f8bc703788d5817da081398fad5dd2'. Error: The request was canceled due to the configured HttpClient.Timeout of 100 seconds elapsing. ... 164: env: 165: PNPM_HOME: /home/runner/setup-pnpm/node_modules/.bin 166: ##[endgroup] 167: Scope: all 59 workspace projects 168: ERR_PNPM_OUTDATED_LOCKFILE  Cannot install with "frozen-lockfile" because pnpm-lock.yaml is not up to date with packages/scalar-app/package.json 169: Note that in CI environments this setting is true by default. If you still need to run install in such cases, use "pnpm install --no-frozen-lockfile" 170: Failure reason: 171: specifiers in the lockfile ({"@electron-toolkit/preload":"^3.0.0","@electron-toolkit/utils":"^3.0.0","@scalar/api-client":"workspace:*","@scalar/components":"workspace:*","@scalar/import":"workspace:*","@scalar/themes":"workspace:*","@todesktop/runtime":"^2.0.0","electron-window-state":"^5.0.3","fathom-client":"^3.7.2","@electron-toolkit/tsconfig":"^1.0.1","@rushstack/eslint-patch":"^1.10.3","@todesktop/cli":"^1.10.5","@types/node":"^20.14.10","@vitejs/plugin-vue":"^5.0.4","@vue/eslint-config-prettier":"^9.0.0","@vue/eslint-config-typescript":"^12.0.0","electron":"^33.2.1","electron-vite":"^2.3.0","vite":"^5.4.10","vue":"^3.5.12","vue-tsc":"^2.1.10"}) don't match specs in package.json ({"@electron-toolkit/tsconfig":"^1.0.1","@rushstack/eslint-patch":"^1.10.3","@todesktop/cli":"^1.11.1","@types/node":"^20.14.10","@vitejs/plugin-vue":"^5.0.4","@vue/eslint-config-prettier":"^9.0.0","@vue/eslint-config-typescript":"^12.0.0","electron":"^33.2.1","electron-vite":"^2.3.0","vite":"^5.4.10","vue":"^3.5.12","vue-tsc":"^2.1.10","@electron-toolkit/preload":"^3.0.0","@electron-toolkit/utils":"^3.0.0","@scalar/api-client":"workspace:*","@scalar/components":"workspace:*","@scalar/import":"workspace:*","@scalar/themes":"workspace:*","@todesktop/runtime":"^2.0.0","electron-window-state":"^5.0.3","fathom-client":"^3.7.2"}) 172: ##[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.