Skip to content

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jan 19, 2026

Bumps the dev-dependencies group with 5 updates:

Package From To
@turbo/gen 2.7.4 2.7.5
@types/node 24.10.7 24.10.9
prettier 3.7.4 3.8.0
turbo 2.7.4 2.7.5
pino 10.1.1 10.2.1

Updates @turbo/gen from 2.7.4 to 2.7.5

Release notes

Sourced from @​turbo/gen's releases.

Turborepo v2.7.5

What's Changed

Docs

create-turbo

Changelog

Full Changelog: vercel/turborepo@v2.7.4...v2.7.5

Turborepo v2.7.5-canary.15

What's Changed

Docs

Full Changelog: vercel/turborepo@v2.7.5-canary.14...v2.7.5-canary.15

Turborepo v2.7.5-canary.14

What's Changed

Changelog

... (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
  2. Builds Rust binaries for 6 different platforms (macOS, Linux, Windows on x64 and ARM64)
  3. Packages native binaries as separate npm packages (e.g., turbo-darwin-64, turbo-linux-arm64)

... (truncated)

Commits

Updates @types/node from 24.10.7 to 24.10.9

Commits

Updates prettier from 3.7.4 to 3.8.0

Release notes

Sourced from prettier's releases.

3.8.0

  • Support Angular v21.1

diff

🔗 Release note "Prettier 3.8: Support for Angular v21.1"

Changelog

Sourced from prettier's changelog.

3.8.0

diff

🔗 Release Notes

Commits

Updates turbo from 2.7.4 to 2.7.5

Release notes

Sourced from turbo's releases.

Turborepo v2.7.5

What's Changed

Docs

create-turbo

Changelog

Full Changelog: vercel/turborepo@v2.7.4...v2.7.5

Turborepo v2.7.5-canary.15

What's Changed

Docs

Full Changelog: vercel/turborepo@v2.7.5-canary.14...v2.7.5-canary.15

Turborepo v2.7.5-canary.14

What's Changed

Changelog

... (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
  2. Builds Rust binaries for 6 different platforms (macOS, Linux, Windows on x64 and ARM64)
  3. Packages native binaries as separate npm packages (e.g., turbo-darwin-64, turbo-linux-arm64)

... (truncated)

Commits

Updates pino from 10.1.1 to 10.2.1

Release notes

Sourced from pino's releases.

v10.2.1

What's Changed

Full Changelog: pinojs/pino@v10.2.0...v10.2.1

v10.2.0

What's Changed

New Contributors

Full Changelog: pinojs/pino@v10.1.1...v10.2.0

Commits

Most Recent Ignore Conditions Applied to This Pull Request
Dependency Name Ignore Conditions
@types/node [>= 25.a, < 26]

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 Jan 19, 2026
@dependabot dependabot bot requested review from a team as code owners January 19, 2026 16:04
@dependabot dependabot bot added dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code labels Jan 19, 2026
@wasmcloud-automation-app
Copy link
Contributor

wasmcloud-automation-app bot commented Jan 19, 2026

Unnecessary Changesets

The following package(s) are private and do not need a changeset:

  • washboard-ui
  • @wasmcloud/eslint-config

Changed Packages

Package Name Package Path Changeset Bump Current Version
washboard-ui apps/washboard-ui patch v0.8.4
@wasmcloud/eslint-config packages/eslint-config patch v0.1.5

Bumps the dev-dependencies group with 5 updates:

| Package | From | To |
| --- | --- | --- |
| [@turbo/gen](https://github.com/vercel/turborepo/tree/HEAD/packages/turbo-gen) | `2.7.4` | `2.7.5` |
| [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node) | `24.10.7` | `24.10.9` |
| [prettier](https://github.com/prettier/prettier) | `3.7.4` | `3.8.0` |
| [turbo](https://github.com/vercel/turborepo) | `2.7.4` | `2.7.5` |
| [pino](https://github.com/pinojs/pino) | `10.1.1` | `10.2.1` |

Updates `@turbo/gen` from 2.7.4 to 2.7.5
- [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.7.5/packages/turbo-gen)

Updates `@types/node` from 24.10.7 to 24.10.9
- [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases)
- [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/node)

Updates `prettier` from 3.7.4 to 3.8.0
- [Release notes](https://github.com/prettier/prettier/releases)
- [Changelog](https://github.com/prettier/prettier/blob/main/CHANGELOG.md)
- [Commits](prettier/prettier@3.7.4...3.8.0)

Updates `turbo` from 2.7.4 to 2.7.5
- [Release notes](https://github.com/vercel/turborepo/releases)
- [Changelog](https://github.com/vercel/turborepo/blob/main/RELEASE.md)
- [Commits](vercel/turborepo@v2.7.4...v2.7.5)

Updates `pino` from 10.1.1 to 10.2.1
- [Release notes](https://github.com/pinojs/pino/releases)
- [Commits](pinojs/pino@v10.1.1...v10.2.1)

---
updated-dependencies:
- dependency-name: "@turbo/gen"
  dependency-version: 2.7.5
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: dev-dependencies
- dependency-name: "@types/node"
  dependency-version: 24.10.9
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: dev-dependencies
- dependency-name: prettier
  dependency-version: 3.8.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: dev-dependencies
- dependency-name: turbo
  dependency-version: 2.7.5
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: dev-dependencies
- dependency-name: pino
  dependency-version: 10.2.1
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: dev-dependencies
...

Signed-off-by: dependabot[bot] <support@github.com>
Signed-off-by: wasmcloud-automation-app[bot] <151542377+wasmcloud-automation-app[bot]@users.noreply.github.com>
@wasmcloud-automation-app wasmcloud-automation-app bot force-pushed the dependabot/npm_and_yarn/dev-dependencies-8902c8e5e9 branch from 3e3dda6 to 08b753b Compare January 19, 2026 16:04
@lachieh lachieh merged commit 02a5184 into main Jan 21, 2026
14 checks passed
@lachieh lachieh deleted the dependabot/npm_and_yarn/dev-dependencies-8902c8e5e9 branch January 21, 2026 14:16
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.

2 participants