Skip to content

Conversation

@dependabot
Copy link

@dependabot dependabot bot commented on behalf of github Dec 8, 2025

Bumps the npm-development group with 8 updates in the / directory:

Package From To
@changesets/cli 2.29.7 2.29.8
@commitlint/cli 20.1.0 20.2.0
@commitlint/config-conventional 20.0.0 20.2.0
@turbo/gen 2.6.1 2.6.3
lint-staged 16.2.6 16.2.7
rimraf 6.1.0 6.1.2
tsx 4.20.6 4.21.0
turbo 2.6.1 2.6.3

Updates @changesets/cli from 2.29.7 to 2.29.8

Commits

Updates @commitlint/cli from 20.1.0 to 20.2.0

Release notes

Sourced from @​commitlint/cli's releases.

v20.2.0

20.2.0 (2025-12-05)

Features

Chore, docs, etc

New Contributors

Full Changelog: conventional-changelog/commitlint@v20.1.0...v20.2.0

Changelog

Sourced from @​commitlint/cli's changelog.

20.2.0 (2025-12-05)

Note: Version bump only for package @​commitlint/cli

Commits

Updates @commitlint/config-conventional from 20.0.0 to 20.2.0

Release notes

Sourced from @​commitlint/config-conventional's releases.

v20.2.0

20.2.0 (2025-12-05)

Features

Chore, docs, etc

New Contributors

Full Changelog: conventional-changelog/commitlint@v20.1.0...v20.2.0

v20.1.0

20.1.0 (2025-09-30)

Features

Bug Fixes

New Contributors

Full Changelog: conventional-changelog/commitlint@v20.0.0...v20.1.0

Changelog

Sourced from @​commitlint/config-conventional's changelog.

20.2.0 (2025-12-05)

Note: Version bump only for package @​commitlint/config-conventional

Commits

Updates @turbo/gen from 2.6.1 to 2.6.3

Release notes

Sourced from @​turbo/gen's releases.

Turborepo v2.6.3

What's Changed

turbo-ignore

Examples

Changelog

New Contributors

Full Changelog: vercel/turborepo@v2.6.2...v2.6.3

Turborepo v2.6.3-canary.0

What's Changed

Changelog

New Contributors

Full Changelog: vercel/turborepo@v2.6.2...v2.6.3-canary.0

Turborepo v2.6.2

What's Changed

Docs

... (truncated)

Changelog

Sourced from @​turbo/gen's changelog.

Release Documentation

Quick Start

Release Turborepo CLI

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

    • Specify the semver increment using the SemVer Increment field (start with prerelease)
    • Check the "Dry Run" box to run the full release workflow without publishing any packages. Artifacts will be created that you can test with locally.
  2. A PR is automatically opened to merge the release branch created in step 1 back into main

    • ⚠️ Merge this in! You don't need to wait for tests to pass (because they won't pass until after this PR is merged in). It's important to merge this branch soon after the publish is successful.

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. Version Management
  3. Release Workflow Stages
  4. Packages Released
  5. Platform-Specific Binaries
  6. Technical Reference
  7. Best Practices

Architecture Overview

The Turborepo release process is a multi-stage pipeline that:

  1. Manages versions centrally via version.txt at the repository root

... (truncated)

Commits
Maintainer changes

This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for @​turbo/gen since your current version.


Updates lint-staged from 16.2.6 to 16.2.7

Release notes

Sourced from lint-staged's releases.

v16.2.7

Patch Changes

  • #1711 ef74c8d Thanks @​iiroj! - Do not display a "failed to spawn" error message when a task fails normally. This message is reserved for when the task didn't run because spawning it failed.
Changelog

Sourced from lint-staged's changelog.

16.2.7

Patch Changes

  • #1711 ef74c8d Thanks @​iiroj! - Do not display a "failed to spawn" error message when a task fails normally. This message is reserved for when the task didn't run because spawning it failed.
Commits
  • 0c1b000 chore(changeset): release
  • 595b202 build(deps): update dependencies
  • ef74c8d fix: do display "failed to spawn" message when task fails normally
  • 5cf2a1e style: do not autofix when running lint-staged
  • ba40012 chore: drop npx from commit-msg hook
  • d67de9a chore: fix pre-push hook usage with changeset
  • 8017d1d build(deps): update dependencies
  • 922d7f4 ci: remove dependabot integration, it's not useful
  • 6aeeef1 docs: add PR template
  • a5728b5 docs: add AGENTS.md
  • Additional commits viewable in compare view

Updates rimraf from 6.1.0 to 6.1.2

Commits

Updates tsx from 4.20.6 to 4.21.0

Release notes

Sourced from tsx's releases.

v4.21.0

4.21.0 (2025-11-30)

Features


This release is also available on:

Commits

Updates turbo from 2.6.1 to 2.6.3

Release notes

Sourced from turbo's releases.

Turborepo v2.6.3

What's Changed

turbo-ignore

Examples

Changelog

New Contributors

Full Changelog: vercel/turborepo@v2.6.2...v2.6.3

Turborepo v2.6.3-canary.0

What's Changed

Changelog

New Contributors

Full Changelog: vercel/turborepo@v2.6.2...v2.6.3-canary.0

Turborepo v2.6.2

What's Changed

Docs

... (truncated)

Changelog

Sourced from turbo's changelog.

Release Documentation

Quick Start

Release Turborepo CLI

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

    • Specify the semver increment using the SemVer Increment field (start with prerelease)
    • Check the "Dry Run" box to run the full release workflow without publishing any packages. Artifacts will be created that you can test with locally.
  2. A PR is automatically opened to merge the release branch created in step 1 back into main

    • ⚠️ Merge this in! You don't need to wait for tests to pass (because they won't pass until after this PR is merged in). It's important to merge this branch soon after the publish is successful.

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. Version Management
  3. Release Workflow Stages
  4. Packages Released
  5. Platform-Specific Binaries
  6. Technical Reference
  7. Best Practices

Architecture Overview

The Turborepo release process is a multi-stage pipeline that:

  1. Manages versions centrally via version.txt at the repository root

... (truncated)

Commits
Maintainer changes

This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~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 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

@dependabot dependabot bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Dec 8, 2025
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/npm-development-5e3280a119 branch 4 times, most recently from ee4a5e1 to 022a1dd Compare December 18, 2025 17:57
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/npm-development-5e3280a119 branch 2 times, most recently from ad08674 to 77d7ceb Compare December 24, 2025 18:22
…th 8 updates

Bumps the npm-development group with 8 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [@changesets/cli](https://github.com/changesets/changesets) | `2.29.7` | `2.29.8` |
| [@commitlint/cli](https://github.com/conventional-changelog/commitlint/tree/HEAD/@commitlint/cli) | `20.1.0` | `20.2.0` |
| [@commitlint/config-conventional](https://github.com/conventional-changelog/commitlint/tree/HEAD/@commitlint/config-conventional) | `20.0.0` | `20.2.0` |
| [@turbo/gen](https://github.com/vercel/turborepo/tree/HEAD/packages/turbo-gen) | `2.6.1` | `2.6.3` |
| [lint-staged](https://github.com/lint-staged/lint-staged) | `16.2.6` | `16.2.7` |
| [rimraf](https://github.com/isaacs/rimraf) | `6.1.0` | `6.1.2` |
| [tsx](https://github.com/privatenumber/tsx) | `4.20.6` | `4.21.0` |
| [turbo](https://github.com/vercel/turborepo) | `2.6.1` | `2.6.3` |



Updates `@changesets/cli` from 2.29.7 to 2.29.8
- [Release notes](https://github.com/changesets/changesets/releases)
- [Commits](https://github.com/changesets/changesets/commits)

Updates `@commitlint/cli` from 20.1.0 to 20.2.0
- [Release notes](https://github.com/conventional-changelog/commitlint/releases)
- [Changelog](https://github.com/conventional-changelog/commitlint/blob/master/@commitlint/cli/CHANGELOG.md)
- [Commits](https://github.com/conventional-changelog/commitlint/commits/v20.2.0/@commitlint/cli)

Updates `@commitlint/config-conventional` from 20.0.0 to 20.2.0
- [Release notes](https://github.com/conventional-changelog/commitlint/releases)
- [Changelog](https://github.com/conventional-changelog/commitlint/blob/master/@commitlint/config-conventional/CHANGELOG.md)
- [Commits](https://github.com/conventional-changelog/commitlint/commits/v20.2.0/@commitlint/config-conventional)

Updates `@turbo/gen` from 2.6.1 to 2.6.3
- [Release notes](https://github.com/vercel/turborepo/releases)
- [Changelog](https://github.com/vercel/turborepo/blob/main/RELEASE.md)
- [Commits](https://github.com/vercel/turborepo/commits/v2.6.3/packages/turbo-gen)

Updates `lint-staged` from 16.2.6 to 16.2.7
- [Release notes](https://github.com/lint-staged/lint-staged/releases)
- [Changelog](https://github.com/lint-staged/lint-staged/blob/main/CHANGELOG.md)
- [Commits](lint-staged/lint-staged@v16.2.6...v16.2.7)

Updates `rimraf` from 6.1.0 to 6.1.2
- [Changelog](https://github.com/isaacs/rimraf/blob/main/CHANGELOG.md)
- [Commits](isaacs/rimraf@v6.1.0...v6.1.2)

Updates `tsx` from 4.20.6 to 4.21.0
- [Release notes](https://github.com/privatenumber/tsx/releases)
- [Changelog](https://github.com/privatenumber/tsx/blob/master/release.config.cjs)
- [Commits](privatenumber/tsx@v4.20.6...v4.21.0)

Updates `turbo` from 2.6.1 to 2.6.3
- [Release notes](https://github.com/vercel/turborepo/releases)
- [Changelog](https://github.com/vercel/turborepo/blob/main/RELEASE.md)
- [Commits](vercel/turborepo@v2.6.1...v2.6.3)

---
updated-dependencies:
- dependency-name: "@changesets/cli"
  dependency-version: 2.29.8
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: npm-development
- dependency-name: "@commitlint/cli"
  dependency-version: 20.2.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: npm-development
- dependency-name: "@commitlint/config-conventional"
  dependency-version: 20.2.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: npm-development
- dependency-name: "@turbo/gen"
  dependency-version: 2.6.3
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: npm-development
- dependency-name: lint-staged
  dependency-version: 16.2.7
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: npm-development
- dependency-name: rimraf
  dependency-version: 6.1.2
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: npm-development
- dependency-name: tsx
  dependency-version: 4.21.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: npm-development
- dependency-name: turbo
  dependency-version: 2.6.3
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: npm-development
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/npm-development-5e3280a119 branch from 77d7ceb to faf0103 Compare December 24, 2025 18:34
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.

1 participant