Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
dependabot wants to merge 1 commit into
base: main
Choose a base branch
from
Open

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

dependabot wants to merge 1 commit into from
+865 −550

Conversation

@dependabot
Copy link

@dependabot dependabot bot commented on behalf of github Dec 1, 2025 •
edited
Loading

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

Package From To
@changesets/cli 2.29.7 2.29.8
@pixpilot/workspace-package-generator 2.1.1 2.1.2
@turbo/gen 2.5.8 2.6.1
lint-staged 16.1.5 16.2.7
rimraf 6.0.1 6.1.2
turbo 2.5.8 2.6.1
ci-info 4.3.0 4.3.1
eslint-plugin-turbo 2.5.8 2.6.1
esbuild 0.25.11 0.27.0

Updates @changesets/cli from 2.29.7 to 2.29.8

Commits

Updates @pixpilot/workspace-package-generator from 2.1.1 to 2.1.2

Release notes

Sourced from @​pixpilot/workspace-package-generator's releases.

@​pixpilot/workspace-package-generator@​2.1.2

@​pixpilot/workspace-package-generator@​2.1.2

Patch Changes

  • update README usage instructions and repository URLs
  • correct usage instructions formatting in README template
Changelog

Sourced from @​pixpilot/workspace-package-generator's changelog.

2.1.2

Patch Changes

  • update README usage instructions and repository URLs
  • correct usage instructions formatting in README template
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.1.5 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.

v16.2.4

Patch Changes

v16.2.3

Patch Changes

  • #1669 27cd541 Thanks @​iiroj! - When using --fail-on-changes, automatically hidden (partially) unstaged changes are no longer counted to make lint-staged fail.

v16.2.2

Patch Changes

  • #1667 699f95d Thanks @​iiroj! - The backup stash will not be dropped when using --fail-on-changes and there are errors. When reverting to original state is disabled (via --no-revert or --fail-on-changes), hidden (partially) unstaged changes are still restored automatically so that it's easier to resolve the situation manually.

    Additionally, the example for using the backup stash manually now uses the correct backup hash, if available:

    % npx lint-staged --fail-on-changes
✔ Backed up original state in git stash (c18d55a3)
✔ Running tasks for staged files...
✖ Tasks modified files and --fail-on-changes was used!
↓ Cleaning up temporary files...
✖ lint-staged failed because --fail-on-changes was used.
Any lost modifications can be restored from a git stash:
> git stash list --format="%h %s"
c18d55a3 On main: lint-staged automatic backup
> git apply --index c18d55a3

... (truncated)

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.

16.2.4

Patch Changes

16.2.3

Patch Changes

  • #1669 27cd541 Thanks @​iiroj! - When using --fail-on-changes, automatically hidden (partially) unstaged changes are no longer counted to make lint-staged fail.

16.2.2

Patch Changes

  • #1667 699f95d Thanks @​iiroj! - The backup stash will not be dropped when using --fail-on-changes and there are errors. When reverting to original state is disabled (via --no-revert or --fail-on-changes), hidden (partially) unstaged changes are still restored automatically so that it's easier to resolve the situation manually.

    Additionally, the example for using the backup stash manually now uses the correct backup hash, if available:

    % npx lint-staged --fail-on-changes
✔ Backed up original state in git stash (c18d55a3)
✔ Running tasks for staged files...
✖ Tasks modified files and --fail-on-changes was used!
↓ Cleaning up temporary files...
✖ lint-staged failed because --fail-on-changes was used.
Any lost modifications can be restored from a git stash:

... (truncated)

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
Maintainer changes

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


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 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 ci-info from 4.3.0 to 4.3.1

Release notes

Sourced from ci-info's releases.

v4.3.1

Bug Fixes

  • don't read envs when CI is set to false 3fae1ac
Changelog

Sourced from ci-info's changelog.

v4.3.1

  • don't read envs when CI is set to false 3fae1ac
Commits
Maintainer changes

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


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

@dependabot
chore(deps-dev): bump the npm-development group across 1 directory wi…
ffbe6b8 
…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` |
| [@pixpilot/workspace-package-generator](https://github.com/pixpilot/pnpm-toolkit/tree/HEAD/packages/workspace-package-generator) | `2.1.1` | `2.1.2` |
| [@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.1.5` | `16.2.7` |
| [rimraf](https://github.com/isaacs/rimraf) | `6.0.1` | `6.1.2` |
| [turbo](https://github.com/vercel/turborepo) | `2.5.8` | `2.6.1` |
| [ci-info](https://github.com/watson/ci-info) | `4.3.0` | `4.3.1` |
| [eslint-plugin-turbo](https://github.com/vercel/turborepo/tree/HEAD/packages/eslint-plugin-turbo) | `2.5.8` | `2.6.1` |
| [esbuild](https://github.com/evanw/esbuild) | `0.25.11` | `0.27.0` |



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 `@pixpilot/workspace-package-generator` from 2.1.1 to 2.1.2
- [Release notes](https://github.com/pixpilot/pnpm-toolkit/releases)
- [Changelog](https://github.com/pixpilot/pnpm-toolkit/blob/main/packages/workspace-package-generator/CHANGELOG.md)
- [Commits](https://github.com/pixpilot/pnpm-toolkit/commits/@pixpilot/workspace-package-generator@2.1.2/packages/workspace-package-generator)

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.1.5 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.1.5...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 `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 `ci-info` from 4.3.0 to 4.3.1
- [Release notes](https://github.com/watson/ci-info/releases)
- [Changelog](https://github.com/watson/ci-info/blob/master/CHANGELOG.md)
- [Commits](watson/ci-info@v4.3.0...v4.3.1)

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)

Updates `esbuild` from 0.25.11 to 0.27.0
- [Release notes](https://github.com/evanw/esbuild/releases)
- [Changelog](https://github.com/evanw/esbuild/blob/main/CHANGELOG.md)
- [Commits](evanw/esbuild@v0.25.11...v0.27.0)

---
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: "@pixpilot/workspace-package-generator"
  dependency-version: 2.1.2
  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-minor
  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: turbo
  dependency-version: 2.6.1
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: npm-development
- dependency-name: ci-info
  dependency-version: 4.3.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
- dependency-name: esbuild
  dependency-version: 0.27.0
  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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

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