Skip to content

Bump the npm_and_yarn group across 2 directories with 1 update#578

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/npm_and_yarn-537042f9dc
Open

Bump the npm_and_yarn group across 2 directories with 1 update#578
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/npm_and_yarn-537042f9dc

Conversation

@dependabot
Copy link
Copy Markdown
Contributor

@dependabot dependabot Bot commented on behalf of github May 20, 2026

Bumps the npm_and_yarn group with 1 update in the / directory: turbo.
Bumps the npm_and_yarn group with 1 update in the /apis/vercel directory: turbo.

Updates turbo from 1.11.2 to 2.9.14

Release notes

Sourced from turbo's releases.

Turborepo v2.9.14

[!NOTE] This release contains important security fixes.

High:

Low:

What's Changed

Changelog

New Contributors

Full Changelog: vercel/turborepo@v2.9.12...v2.9.14

Turborepo v2.9.13-canary.1

What's Changed

Changelog

... (truncated)

Changelog

Sourced from turbo's changelog.

Release Documentation

Quick Start

Automated Canary Releases

Canary releases run on an hourly schedule via the [Release workflow][1]:

  1. Runs every hour via cron, skipping if no relevant files (crates/, packages/, cli/) changed since the last canary tag
  2. Skips if the latest commit is a release PR merge (to avoid releasing the version bump itself)
  3. Publishes to npm with the canary tag
  4. Opens a PR with auto-merge enabled to merge the version bump back to main

No manual intervention required for canary releases.

Manual Releases (Stable/Custom)

  1. Create a release by triggering the [Turborepo Release][1] workflow

    • For stable releases, use patch, minor, or major
    • For custom pre-releases, use prepatch, preminor, or premajor
    • Check the "Dry Run" box to test the workflow without publishing
  2. A PR is automatically opened to merge the release branch back into main

    • Merge this promptly to avoid conflicts

Release @turbo/repository

  1. Run [bump-version.sh][4] to update the versions of the packages. Merge in the changes to main.

  2. Create a release by triggering the [Turborepo Library Release][5] workflow.

    • Check the "Dry Run" box to run the full release workflow without publishing any packages.

Notes

  • GitHub Release Notes are published automatically using the config from [turborepo-release.yml][2], triggered by the [turbo-orchestrator][3] bot.

Turborepo CLI Release Process - In-Depth Guide

This section provides comprehensive documentation on how the Turborepo CLI is released, including the architecture, workflows, and detailed step-by-step processes.

Table of Contents

  1. Architecture Overview
  2. Automated Canary Releases
  3. Version Management
  4. Release Workflow Stages
  5. Packages Released

... (truncated)

Commits
Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for turbo since your current version.


Updates turbo from 1.11.2 to 2.9.14

Release notes

Sourced from turbo's releases.

Turborepo v2.9.14

[!NOTE] This release contains important security fixes.

High:

Low:

What's Changed

Changelog

New Contributors

Full Changelog: vercel/turborepo@v2.9.12...v2.9.14

Turborepo v2.9.13-canary.1

What's Changed

Changelog

... (truncated)

Changelog

Sourced from turbo's changelog.

Release Documentation

Quick Start

Automated Canary Releases

Canary releases run on an hourly schedule via the [Release workflow][1]:

  1. Runs every hour via cron, skipping if no relevant files (crates/, packages/, cli/) changed since the last canary tag
  2. Skips if the latest commit is a release PR merge (to avoid releasing the version bump itself)
  3. Publishes to npm with the canary tag
  4. Opens a PR with auto-merge enabled to merge the version bump back to main

No manual intervention required for canary releases.

Manual Releases (Stable/Custom)

  1. Create a release by triggering the [Turborepo Release][1] workflow

    • For stable releases, use patch, minor, or major
    • For custom pre-releases, use prepatch, preminor, or premajor
    • Check the "Dry Run" box to test the workflow without publishing
  2. A PR is automatically opened to merge the release branch back into main

    • Merge this promptly to avoid conflicts

Release @turbo/repository

  1. Run [bump-version.sh][4] to update the versions of the packages. Merge in the changes to main.

  2. Create a release by triggering the [Turborepo Library Release][5] workflow.

    • Check the "Dry Run" box to run the full release workflow without publishing any packages.

Notes

  • GitHub Release Notes are published automatically using the config from [turborepo-release.yml][2], triggered by the [turbo-orchestrator][3] bot.

Turborepo CLI Release Process - In-Depth Guide

This section provides comprehensive documentation on how the Turborepo CLI is released, including the architecture, workflows, and detailed step-by-step processes.

Table of Contents

  1. Architecture Overview
  2. Automated Canary Releases
  3. Version Management
  4. Release Workflow Stages
  5. Packages Released

... (truncated)

Commits
Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for turbo since your current version.


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 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
    You can disable automated security fix PRs for this repo from the Security Alerts page.

Bumps the npm_and_yarn group with 1 update in the / directory: [turbo](https://github.com/vercel/turborepo).
Bumps the npm_and_yarn group with 1 update in the /apis/vercel directory: [turbo](https://github.com/vercel/turborepo).


Updates `turbo` from 1.11.2 to 2.9.14
- [Release notes](https://github.com/vercel/turborepo/releases)
- [Changelog](https://github.com/vercel/turborepo/blob/main/RELEASE.md)
- [Commits](vercel/turborepo@v1.11.2...v2.9.14)

Updates `turbo` from 1.11.2 to 2.9.14
- [Release notes](https://github.com/vercel/turborepo/releases)
- [Changelog](https://github.com/vercel/turborepo/blob/main/RELEASE.md)
- [Commits](vercel/turborepo@v1.11.2...v2.9.14)

---
updated-dependencies:
- dependency-name: turbo
  dependency-version: 2.9.14
  dependency-type: direct:development
  dependency-group: npm_and_yarn
- dependency-name: turbo
  dependency-version: 2.9.14
  dependency-type: direct:development
  dependency-group: npm_and_yarn
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels May 20, 2026
@vercel
Copy link
Copy Markdown

vercel Bot commented May 20, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
ai-proxy Ready Ready Preview, Comment May 20, 2026 12:35am

Request Review

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants