Skip to content

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

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

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

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 1, 2026 •

Copy link
Copy Markdown
Contributor

Bumps turbo from 1.13.4 to 2.9.14.

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 in crates/ or packages/ 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 and merges a PR to return the version bump to main after required checks pass

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 and merged into main after its required workflows are approved and pass.

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.
    • The release PR is automatically merged after its required workflows are approved and pass.

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 requested a review from anuragxxd as a code owner November 1, 2026 14:45
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Nov 1, 2026
@dependabot
dependabot Bot requested a review from uniqueg as a code owner November 1, 2026 14:45
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/turbo-2.9.14 branch from 8fa3b2c to ba7a521 Compare November 1, 2026 15:05
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 ba7a521 to 545c6ac Compare November 1, 2026 16:23

This branch has not been deployed

No deployments
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