[Snyk] Upgrade turbo from 1.11.0 to 1.13.4

[rflihxyz]

Snyk has created this PR to upgrade turbo from 1.11.0 to 1.13.4.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

---

• The recommended version is 49 versions ahead of your current version.

• The recommended version was released on 5 months ago.

Release notes

Package name: turbo

• 1.13.4 - 2024-06-04
  

  What's Changed

  Docs

  • Update eslint-config package name. by @ anthonyshew in #8069
  • chore(docs): add missing words by @ jeremyadavis in #8067
  • Fix typo in Turborepo task-graph documentation by @ danisal in #8212

  turbo-ignore

  • feat(turbo-ignore): don’t fail on single package repos by @ tknickman in #8177

  @ turbo/repository

  • chore: differentiate rust changes from building turbo by @ chris-olszewski in #8001

  Examples

  • fix(examples): lint docs by @ tknickman in #8049
  • fix(example): Fix Prisma example by @ caaatisgood in #8046
  • chore: move react from devDependency to dependency in design system starter template by @ ghdtjgus76 in #8159

  Changelog

  • feat(Turborepo): Be explicit about which binary we failed to find by @ gsoltis in #8050
  • fix(ui): add carraige return after cache log messages by @ chris-olszewski in #8015
  • fix(turborepo): Watch mode not responding to changes by @ NicholasLYang in #8057
  • fix(Turborepo): Make package discovery async, and apply a debouncer by @ gsoltis in #8058
  • fix(Turborepo): Disable inputs support by @ gsoltis in #8074
  • feat(Turborepo): Add support for $TURBO_DEFAULT$ to file hash watcher by @ gsoltis in #8086
  • Remove async-trait from a few crates by @ arlyon in #8077
  • feat(turborepo): Using file hashing for package watching by @ NicholasLYang in #8104
  • add support for cache_timeout as well as timeout by @ arlyon in #8078
  • yield a different warning when the cache upload times out by @ arlyon in #8079
  • fix lockfile by @ sokra in #8110
  • fix(gen): isolate generator to commonjs by @ wesleycoder in #8109
  • fix: properly propigate internal errors by @ chris-olszewski in #8113
  • feat(ui): render ui to alternative screen by @ chris-olszewski in #8084
  • fix(turborepo): Persistent tasks in watch mode by @ NicholasLYang in #8107
  • fix(Turborepo): Fix as_inputs to include ! by @ gsoltis in #8119
  • fix(Turborepo): Handle new packages in lockfile comparisons by @ gsoltis in #8127
  • fix(ui): minor formatting by @ chris-olszewski in #8136
  • feat(turborepo): new ui + watch mode by @ NicholasLYang in #7962
  • fix(turborepo): use transitive closure of filtered packages in watch mode by @ NicholasLYang in #8161
  • add two retry strategies to allow requests to timeout gracefully by @ arlyon in #8080
  • add support for upload speed / remaining in the cache upload step by @ arlyon in #8081
  • chore(@ turbo/benchmark): fix lint warnings by @ mehulkar in #8233
  • chore(turborepo): Feature flagged off file hashing by @ NicholasLYang in #8229
  • chore: downgrade curl to fix Windows rust tests by @ chris-olszewski in #8242
  • fix(turborepo): Remove optional git locks by @ NicholasLYang in #8244
  • fix(turborepo): Optional lock with env var by @ NicholasLYang in #8247

  New Contributors

  • @ caaatisgood made their first contribution in #8046
  • @ jeremyadavis made their first contribution in #8067
  • @ wesleycoder made their first contribution in #8109
  • @ ghdtjgus76 made their first contribution in #8159
  • @ danisal made their first contribution in #8212

  Full Changelog: v1.13.3...v1.13.4

• 1.13.4-canary.5 - 2024-05-20
• 1.13.4-canary.4 - 2024-05-14
• 1.13.4-canary.3 - 2024-05-09
• 1.13.4-canary.2 - 2024-05-08
• 1.13.4-canary.1 - 2024-05-07
• 1.13.4-canary.0 - 2024-04-30
• 1.13.3 - 2024-04-25
• 1.13.3-canary.4 - 2024-04-22
• 1.13.3-canary.3 - 2024-04-19
• 1.13.3-canary.2 - 2024-04-17
• 1.13.3-canary.1 - 2024-04-16
• 1.13.3-canary.0 - 2024-04-02
• 1.13.2 - 2024-04-02
• 1.13.1 - 2024-04-01
• 1.13.1-canary.3 - 2024-03-26
• 1.13.1-canary.2 - 2024-03-25
• 1.13.1-canary.1 - 2024-03-25
• 1.13.1-canary.0 - 2024-03-21
• 1.13.0 - 2024-03-21
• 1.13.0-canary.4 - 2024-03-21
• 1.13.0-canary.3 - 2024-03-20
• 1.13.0-canary.1 - 2024-03-19
• 1.13.0-canary.0 - 2024-03-18
• 1.12.5 - 2024-03-06
• 1.12.5-canary.2 - 2024-03-06
• 1.12.5-canary.1 - 2024-03-05
• 1.12.5-canary.0 - 2024-02-21
• 1.12.4 - 2024-02-14
• 1.12.4-canary.1 - 2024-02-13
• 1.12.4-canary.0 - 2024-02-09
• 1.12.3 - 2024-02-06
• 1.12.3-canary.0 - 2024-02-01
• 1.12.2 - 2024-01-31
• 1.12.1 - 2024-01-31
• 1.12.0 - 2024-01-30
• 1.11.4-canary.4 - 2024-01-30
• 1.11.4-canary.3 - 2024-01-29
• 1.11.4-canary.2 - 2024-01-22
• 1.11.4-canary.1 - 2024-01-12
• 1.11.4-canary.0 - 2024-01-09
• 1.11.3 - 2024-01-04
• 1.11.3-canary.2 - 2024-01-04
• 1.11.3-canary.1 - 2023-12-20
• 1.11.3-canary.0 - 2023-12-13
• 1.11.2 - 2023-12-12
• 1.11.2-canary.0 - 2023-12-11
• 1.11.1 - 2023-12-07
• 1.11.1-canary.0 - 2023-12-07
• 1.11.0 - 2023-12-05

from turbo GitHub release notes

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

• 🧐 View latest project report
• 📜 Customise PR templates
• 🛠 Adjust upgrade PR settings
• 🔕 Ignore this dependency or unsubscribe from future upgrade PRs

[changeset-bot]

⚠️ No Changeset found

Latest commit: 8b01b5c

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

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[coderabbitai]

Important

Review skipped

Ignore keyword(s) in the title.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. 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.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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 or @coderabbitai title 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.

[zeropath-ai]

✅ No security or compliance issues detected. Reviewed everything up to 8b01b5c.

Security Overview

• 🔎 Scanned files: 2 changed file(s)

Detected Code Changes

Change Type	Relevant files
Enhancement	► package.json     Upgrade turbo from 1.10.16 to 1.13.4 ► package-lock.json     Update dependencies for turbo upgrade

Reply to this PR with @zeropath-ai followed by a description of what change you want and we'll auto-submit a change to this PR to implement it.

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source	CI
Non-permissive License	npm/[email protected]	Location: Package overview	package-lock.json package.json pnpm-lock.yaml	⚠︎
Non-permissive License	npm/[email protected]	Location: Package overview	package-lock.json package.json pnpm-lock.yaml	⚠︎
Non-permissive License	npm/[email protected]	Location: Package overview	package-lock.json package.json pnpm-lock.yaml	⚠︎
Non-permissive License	npm/[email protected]	Location: Package overview	package-lock.json package.json pnpm-lock.yaml	⚠︎
Non-permissive License	npm/[email protected]	Location: Package overview	package-lock.json package.json pnpm-lock.yaml	⚠︎
Non-permissive License	npm/[email protected]	Location: Package overview	package-lock.json package.json pnpm-lock.yaml	⚠︎

View full report↗︎

Next steps

What do I need to know about license files?

(Experimental) A license not known to be considered permissive was found.

Determine whether use of material not offered under a known permissive license works for you

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/[email protected] or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]