Skip to content

chore(deps): update all major dependencies (major) - #167

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/major-all-major-dependencies
Open

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/major-all-major-dependencies

Conversation

@renovate

@renovate renovate Bot commented Jun 13, 2026 •

Copy link
Copy Markdown
Contributor

Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence Type Update Pending
@codspeed/vitest-plugin (source) 5.7.1 → 6.1.0 age confidence pnpm.catalog.default major 6.1.1
@vitest/coverage-v8 (source) 4.1.11 → 5.0.5 age confidence pnpm.catalog.default major 5.1.0
electron 44.7.0 → 45.2.1 age confidence pnpm.catalog.default major 45.2.3 (+1)
node (source) ^24.11.0 → ^26.0.0 age confidence engines major
typescript (source) 6.0.3 → 7.0.2 age confidence pnpm.catalog.default major
vite (source) 7.3.7 → 8.3.5 age confidence pnpm.catalog.default major 8.3.6
vitest (source) 4.1.11 → 5.0.5 age confidence pnpm.catalog.default major 5.1.0

Release Notes

CodSpeedHQ/codspeed-node (@​codspeed/vitest-plugin)

v6.1.0

Compare Source

[!IMPORTANT]
CPU Simulation results change for Vitest 5 benchmarks. This release fixes a bug in @codspeed/vitest-plugin where Vitest 5 export getter tracking ran inside the measured code, inflating the measured cost of benchmarks that read module exports. The plugin now sets benchmark.suppressExportGetterWarnings to true by default, unless you set it explicitly. Even though this is a minor release, expect CPU Simulation results for Vitest 5 benchmarks to differ from those measured with 6.0.0 and 6.0.1. Benchmarks on Vitest 3 and 4 are unaffected.

What's Changed

Full Changelog: CodSpeedHQ/codspeed-node@v6.0.1...v6.1.0

v6.0.1

Compare Source

CodSpeed for Node.js 6.0.1 loads again on Linux arm64 systems with an older libstdc++, such as Ubuntu 22.04 and Debian 12. In 6.0.0, the native addon failed there with version 'CXXABI_1.3.15' not found (#​96).

What's Changed

Full Changelog: CodSpeedHQ/codspeed-node@v6.0.0...v6.0.1

v6.0.0

Compare Source

CodSpeed for Node.js 6.0.0 adds support for Node.js 24 and 26, Vitest 5 and Vite 8.

Highlights

Node.js 24 and 26

The plugins now ship prebuilt native addons for Node.js 22, 24 and 26, and warn in CI when running on an untested major.

Vitest 5

@codspeed/vitest-plugin supports Vitest 3, 4 and 5 with no configuration change. On Vitest 5, declare benchmarks with the bench test fixture. Each benchmark passed to bench.compare() is reported as its own benchmark in CodSpeed:

import { test } from "vitest";
import { fibonacci } from "./fibonacci";

test("fibo", async ({ bench }) => {
  await bench("fibo 10", () => {
    fibonacci(10);
  }).run();
  await bench("fibo 15", () => {
    fibonacci(15);
  }).run();
});

To compare implementations side by side, pass them to bench.compare() instead. Each benchmark in the group is still reported as its own benchmark in CodSpeed.

Check out the docs for more information!

Breaking changes

  • Node.js 22 or later is now required.
  • The CPU simulation instrument now disables Maglev on Node.js 24 and later, so hot functions tier up as they do on Node.js 22, and suppresses V8's minor GC task. Expect a one-time change in measured values after upgrading.

What's Changed

New Contributors

Full Changelog: CodSpeedHQ/codspeed-node@v5.7.1...v6.0.0

vitest-dev/vitest (@​vitest/coverage-v8)

v5.0.5

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v5.0.4

Compare Source

   🚀 Features
   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub

v5.0.3

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v5.0.2

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v5.0.1

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v5.0.0

Compare Source

Vitest 5 is officially out! This release focuses on performance and brings a lot of new features while fixing long-standing bugs. See our blog post for the official announcement.

   🚨 Breaking Changes

[!IMPORTANT]
✂ PR body was truncated to here.

@semanticdiff-com

semanticdiff-com Bot commented Jun 13, 2026 •

Copy link
Copy Markdown

Review changes with  SemanticDiff

Changed Files
File Status
  pnpm-workspace.yaml  25% smaller
  package.json  0% smaller
  pnpm-lock.yaml Unsupported file format

@greptile-apps

greptile-apps Bot commented Jun 13, 2026

Copy link
Copy Markdown

Greptile Summary

Updates hoverkraft-tech/compose-action from v2.6.0 to v3.0.0 in the Docker setup composite action. The only breaking change in v3 is that the action now runs on Node 24 instead of Node 20; all public inputs and outputs remain the same.

  • The action reference is correctly pinned to the new full commit SHA (11beaa1c2dae4e8ed7b1665aa074723b6cecb0e4) with an inline version comment, consistent with the repo's pinning convention.
  • The compose-file and up-flags inputs used in this repo are unchanged across the major version boundary, so no usage-side adjustments are needed.

Confidence Score: 5/5

Safe to merge — the update swaps one commit SHA for another with no interface changes, and the only internal difference is a Node runtime upgrade inside the action itself.

The change is a single-line SHA bump. The v3 release notes confirm there are no API-level changes: compose-file, up-flags, and env inputs all work identically. The new commit hash is properly verified against the v3.0.0 tag.

No files require special attention.

Important Files Changed

Filename Overview
.github/actions/setup-docker/action.yaml Bumps hoverkraft-tech/compose-action from v2.6.0 to v3.0.0, pinned to the new commit hash; inputs and usage are unchanged.

Reviews (1): Last reviewed commit: "chore(deps): update all major dependenci..." | Re-trigger Greptile

@codspeed

codspeed Bot commented Jun 13, 2026 •

Copy link
Copy Markdown

Merging this PR will not alter performance

✅ 15 untouched benchmarks


Comparing renovate/major-all-major-dependencies (4ec74ed) with main (32fd41a)

Open in CodSpeed

@codecov

codecov Bot commented Jun 13, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@renovate
renovate Bot force-pushed the renovate/major-all-major-dependencies branch from 6b6a6c7 to 374dd39 Compare June 14, 2026 04:27
@renovate renovate Bot changed the title chore(deps): update all major dependencies to v3 chore(deps): update all major dependencies (major) Jun 14, 2026
@renovate
renovate Bot force-pushed the renovate/major-all-major-dependencies branch from 374dd39 to cb04244 Compare June 24, 2026 18:54
@renovate
renovate Bot force-pushed the renovate/major-all-major-dependencies branch from cb04244 to 4b51f75 Compare June 25, 2026 16:36
@socket-security

socket-security Bot commented Jul 7, 2026 •

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Updatednpm/​@​vitest/​coverage-v8@​4.1.11 ⏵ 5.0.59910079 +198100
Updatednpm/​vitest@​4.1.11 ⏵ 5.0.59810079 +199100
Updatednpm/​vite@​7.3.7 ⏵ 8.3.599 +110082 +198 +1100
Updatednpm/​typescript@​6.0.3 ⏵ 7.0.29910089 -1100100 +10
Updatednpm/​@​codspeed/​vitest-plugin@​5.7.1 ⏵ 6.1.0100 +3100100 +396 +1100
Updatednpm/​electron@​44.7.0 ⏵ 45.2.197 -2100 +16100 +198100

View full report

@renovate
renovate Bot force-pushed the renovate/major-all-major-dependencies branch from 8ae5e9e to 4ec74ed Compare July 14, 2026 21:35
@renovate
renovate Bot force-pushed the renovate/major-all-major-dependencies branch from 4ec74ed to 37abafa Compare July 15, 2026 16:13
@renovate
renovate Bot force-pushed the renovate/major-all-major-dependencies branch from 37abafa to 829b3fd Compare July 21, 2026 05:09

This branch had an error being deployed

1 failed deployment
ci — 50609569 Deployed Nov 7, 2026 by renovate[bot] via Build and test (windows-2025) #1755
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants