Skip to content

chore(deps-dev): bump turbo from 1.13.4 to 2.9.14#595

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/turbo-2.9.14
Open

chore(deps-dev): bump turbo from 1.13.4 to 2.9.14#595
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/turbo-2.9.14

Conversation

@dependabot
Copy link
Copy Markdown

@dependabot dependabot Bot commented on behalf of github May 19, 2026 •
edited
Loading

Bumps turbo from 1.13.4 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 dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code labels May 19, 2026
@dependabot
chore(deps-dev): bump turbo from 1.13.4 to 2.9.14
744f5b0 
Bumps [turbo](https://github.com/vercel/turborepo) from 1.13.4 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.13.4...v2.9.14)

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

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot force-pushed the dependabot/npm_and_yarn/turbo-2.9.14 branch from 74aa386 to 744f5b0 Compare May 21, 2026 05:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

@jokerttu jokerttu

Labels

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

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@jokerttu