Skip to content

chore(deps-dev): bump the npm-development group across 1 directory with 9 updates#45

Closed
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/npm_and_yarn/npm-development-3b9a62fbbf
Closed

chore(deps-dev): bump the npm-development group across 1 directory with 9 updates#45
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/npm_and_yarn/npm-development-3b9a62fbbf

Conversation

@dependabot
Copy link
Copy Markdown

@dependabot dependabot Bot commented on behalf of github Dec 1, 2025

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

Package From To
@changesets/cli 2.29.7 2.29.8
@turbo/gen 2.5.8 2.6.1
lint-staged 16.2.4 16.2.7
rimraf 6.0.1 6.1.2
tsx 4.20.6 4.21.0
turbo 2.5.8 2.6.1
eslint-plugin-jest 29.0.1 29.2.1
eslint-plugin-react-hooks 7.0.0 7.0.1
eslint-plugin-turbo 2.5.8 2.6.1

Updates @changesets/cli from 2.29.7 to 2.29.8

Commits

Updates @turbo/gen from 2.5.8 to 2.6.1

Release notes

Sourced from @​turbo/gen's releases.

Turborepo v2.6.1

What's Changed

Docs

@​turbo/codemod

@​turbo/repository

Examples

Changelog

New Contributors

... (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

Updates lint-staged from 16.2.4 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.

v16.2.6

Patch Changes

  • #1693 33d4502 Thanks @​Adrian-Baran-GY! - Fix problems with --continue-on-error option, where tasks might have still been killed (SIGINT) when one of them failed.

v16.2.5

Patch Changes

  • #1687 9e02d9d Thanks @​iiroj! - Fix unhandled promise rejection when spawning tasks (instead of the tasks themselves failing). Previously when a task failed to spawn, lint-staged also failed and the backup stash might not have been automatically restored.
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.

16.2.6

Patch Changes

  • #1693 33d4502 Thanks @​Adrian-Baran-GY! - Fix problems with --continue-on-error option, where tasks might have still been killed (SIGINT) when one of them failed.

16.2.5

Patch Changes

  • #1687 9e02d9d Thanks @​iiroj! - Fix unhandled promise rejection when spawning tasks (instead of the tasks themselves failing). Previously when a task failed to spawn, lint-staged also failed and the backup stash might not have been automatically restored.
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.0.1 to 6.1.2

Changelog

Sourced from rimraf's changelog.

6.1

  • Move to native fs/promises usage instead of promisifying manually.

6.0

  • Drop support for nodes before v20
  • Add --version to CLI

5.0

  • No default export, only named exports

4.4

  • Provide Dirent or Stats object as second argument to filter

4.3

  • Return boolean indicating whether the path was fully removed
  • Add filter option
  • bin: add --verbose, -v to print files as they are deleted
  • bin: add --no-verbose, -V to not print files as they are deleted
  • bin: add -i --interactive to be prompted on each deletion
  • bin: add -I --no-interactive to not be prompted on each deletion
  • 4.3.1 Fixed inappropriately following symbolic links to directories

v4.2

  • Brought back glob support, using the new and improved glob v9

v4.1

  • Improved hybrid module with no need to look at the .default dangly bit. .default preserved as a reference to rimraf for compatibility with anyone who came to rely on it in v4.0.
  • Accept and ignore -rf and -fr arguments to the bin.

v4.0

  • Remove glob dependency entirely. This library now only accepts actual file and folder names to delete.
  • Accept array of paths or single path.
  • Windows performance and reliability improved.
  • All strategies separated into explicitly exported methods.
  • Drop support for Node.js below version 14
  • rewrite in TypeScript

... (truncated)

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.5.8 to 2.6.1

Release notes

Sourced from turbo's releases.

Turborepo v2.6.1

What's Changed

Docs

@​turbo/codemod

@​turbo/repository

Examples

Changelog

New Contributors

... (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
  • 59685c8 publish 2.6.1 to registry
  • 0270af8 feat: Cross-platform microfrontends port command (#11098)
  • 1de3775 feat: Move icon to left side in TUI (#11097)
  • bd53f07 release(turborepo): 2.6.1-canary.3 (#11096)
  • bf9db59 fix: Improve version resolution in Bun lockfiles (#11095)
  • 23641b7 examples(deps): bump next from 16.0.0 to 16.0.1 in /examples/kitchen-sink (#1...
  • 0646e04 examples(dev-deps): bump svelte from 5.43.3 to 5.43.5 in /examples/with-svelt...
  • ee469d4 release(turborepo): 2.6.1-canary.2 (#11093)
  • 1c99fc9 fix: Bun lockfile pruner adjustment (#11092)
  • 58ba6a7 docs: Fix grammatical mistake on structuring-a-repository.mdx (#11091)
  • Additional commits viewable in compare view

Updates eslint-plugin-jest from 29.0.1 to 29.2.1

Release notes

Sourced from eslint-plugin-jest's releases.

v29.2.1

29.2.1 (2025-11-23)

Bug Fixes

  • valid-mock-module-path: report on ERR_PACKAGE_PATH_NOT_EXPORTED errors (#1860) (6cd4e89)

v29.2.0

29.2.0 (2025-11-20)

Features

v29.1.0

29.1.0 (2025-11-10)

Features

  • prefer-lowercase-title: allow ignoring todos (#1843) (4658638)

v29.0.2-next.1

29.0.2-next.1 (2025-10-31)

Bug Fixes

  • only specify ts-eslint once in package.json (bc1d010)
Changelog

Sourced from eslint-plugin-jest's changelog.

29.2.1 (2025-11-23)

Bug Fixes

  • valid-mock-module-path: report on ERR_PACKAGE_PATH_NOT_EXPORTED errors (#1860) (6cd4e89)

29.2.0 (2025-11-20)

Features

29.1.0 (2025-11-10)

Features

  • prefer-lowercase-title: allow ignoring todos (#1843) (4658638)
Commits
  • 0694024 chore(release): 29.2.1 [skip ci]
  • 6cd4e89 fix(valid-mock-module-path): report on ERR_PACKAGE_PATH_NOT_EXPORTED errors...
  • ba20c35 chore(deps): update yarn to v4.12.0 (#1859)
  • 8a40433 chore(deps): update actions/checkout action to v6 (#1855)
  • 730c3ee chore(release): 29.2.0 [skip ci]
  • a8625f1 feat: create new valid-mock-module-path rule (#1845)
  • 59927d9 ci: don't update uses-with in actions (#1856)
  • 589917a chore(deps): update actions/checkout action to v5.0.1 (#1854)
  • 19dc911 chore(deps): lock file maintenance (#1853)
  • 4851e6b chore(release): 29.1.0 [skip ci]
  • Additional commits viewable in compare view
Maintainer changes

This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for eslint-plugin-jest since your current version.


Updates eslint-plugin-react-hooks from 7.0.0 to 7.0.1

Changelog

Sourced from eslint-plugin-react-hooks's changelog.

7.0.1

  • Disallowed passing inline useEffectEvent values as JSX props to guard against accidental propagation. (#34820 by @​jf-eirinha)
  • Switch to export = so eslint-plugin-react-hooks emits correct types for consumers in Node16 ESM projects. (#34949 by @​karlhorky)
  • Tightened the typing of configs.flat so the configs export is always defined. (#34950 by @​poteto)
  • Fix named import runtime errors. (#34951, #34953 by @​karlhorky)
Commits

Updates eslint-plugin-turbo from 2.5.8 to 2.6.1

Release notes

Sourced from eslint-plugin-turbo's releases.

Turborepo v2.6.1

What's Changed

Docs

@​turbo/codemod

@​turbo/repository

Examples

Changelog

New Contributors

... (truncated)

Changelog

Sourced from eslint-plugin-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

…th 9 updates

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

| Package | From | To |
| --- | --- | --- |
| [@changesets/cli](https://github.com/changesets/changesets) | `2.29.7` | `2.29.8` |
| [@turbo/gen](https://github.com/vercel/turborepo/tree/HEAD/packages/turbo-gen) | `2.5.8` | `2.6.1` |
| [lint-staged](https://github.com/lint-staged/lint-staged) | `16.2.4` | `16.2.7` |
| [rimraf](https://github.com/isaacs/rimraf) | `6.0.1` | `6.1.2` |
| [tsx](https://github.com/privatenumber/tsx) | `4.20.6` | `4.21.0` |
| [turbo](https://github.com/vercel/turborepo) | `2.5.8` | `2.6.1` |
| [eslint-plugin-jest](https://github.com/jest-community/eslint-plugin-jest) | `29.0.1` | `29.2.1` |
| [eslint-plugin-react-hooks](https://github.com/facebook/react/tree/HEAD/packages/eslint-plugin-react-hooks) | `7.0.0` | `7.0.1` |
| [eslint-plugin-turbo](https://github.com/vercel/turborepo/tree/HEAD/packages/eslint-plugin-turbo) | `2.5.8` | `2.6.1` |



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 `@turbo/gen` from 2.5.8 to 2.6.1
- [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.1/packages/turbo-gen)

Updates `lint-staged` from 16.2.4 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.4...v16.2.7)

Updates `rimraf` from 6.0.1 to 6.1.2
- [Changelog](https://github.com/isaacs/rimraf/blob/main/CHANGELOG.md)
- [Commits](isaacs/rimraf@v6.0.1...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.5.8 to 2.6.1
- [Release notes](https://github.com/vercel/turborepo/releases)
- [Changelog](https://github.com/vercel/turborepo/blob/main/RELEASE.md)
- [Commits](vercel/turborepo@v2.5.8...v2.6.1)

Updates `eslint-plugin-jest` from 29.0.1 to 29.2.1
- [Release notes](https://github.com/jest-community/eslint-plugin-jest/releases)
- [Changelog](https://github.com/jest-community/eslint-plugin-jest/blob/main/CHANGELOG.md)
- [Commits](jest-community/eslint-plugin-jest@v29.0.1...v29.2.1)

Updates `eslint-plugin-react-hooks` from 7.0.0 to 7.0.1
- [Release notes](https://github.com/facebook/react/releases)
- [Changelog](https://github.com/facebook/react/blob/main/packages/eslint-plugin-react-hooks/CHANGELOG.md)
- [Commits](https://github.com/facebook/react/commits/HEAD/packages/eslint-plugin-react-hooks)

Updates `eslint-plugin-turbo` from 2.5.8 to 2.6.1
- [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.1/packages/eslint-plugin-turbo)

---
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: "@turbo/gen"
  dependency-version: 2.6.1
  dependency-type: direct:development
  update-type: version-update:semver-minor
  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-minor
  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.1
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: npm-development
- dependency-name: eslint-plugin-jest
  dependency-version: 29.2.1
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: npm-development
- dependency-name: eslint-plugin-react-hooks
  dependency-version: 7.0.1
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: npm-development
- dependency-name: eslint-plugin-turbo
  dependency-version: 2.6.1
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: npm-development
...

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 Dec 1, 2025
@dependabot @github
Copy link
Copy Markdown
Author

dependabot Bot commented on behalf of github Dec 8, 2025

Looks like these dependencies are updatable in another way, so this is no longer needed.

@dependabot dependabot Bot closed this Dec 8, 2025
@dependabot dependabot Bot deleted the dependabot/npm_and_yarn/npm-development-3b9a62fbbf branch December 8, 2025 03:24
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