Skip to content

Update npm dependencies (major)#59

Open
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/major-npm-dependencies
Open

Update npm dependencies (major)#59
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/major-npm-dependencies

Conversation

@renovate
Copy link
Copy Markdown

@renovate renovate Bot commented Apr 24, 2026

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
@actions/core (source) ^1.11.1^3.0.0 age confidence
typescript (source) ^5.7.0^6.0.0 age confidence
undici (source) ^6.24.0^8.0.0 age confidence
vite (source) ^7.3.2^8.0.0 age confidence
vitest (source) ^3.0.0^4.0.0 age confidence

Release Notes

actions/toolkit (@​actions/core)

v3.0.1

  • Bump undici from 6.23.0 to 6.24.1 #​2348

v3.0.0

  • Breaking change: Package is now ESM-only
    • CommonJS consumers must use dynamic import() instead of require()

v2.0.3

  • Bump @actions/http-client to 3.0.2

v2.0.1

v2.0.0

microsoft/TypeScript (typescript)

v6.0.3

Compare Source

v6.0.2

Compare Source

nodejs/undici (undici)

v8.3.0

Compare Source

What's Changed

New Contributors

Full Changelog: nodejs/undici@v8.2.0...v8.3.0

v8.2.0

Compare Source

What's Changed

New Contributors

Full Changelog: nodejs/undici@v8.1.0...v8.2.0

v8.1.0

Compare Source

What's Changed

Full Changelog: nodejs/undici@v8.0.3...v8.1.0

v8.0.3

Compare Source

What's Changed

New Contributors

Full Changelog: nodejs/undici@v8.0.2...v8.0.3

v8.0.2

Compare Source

What's Changed

Full Changelog: nodejs/undici@v8.0.1...v8.0.2

v8.0.1

Compare Source

What's Changed

New Contributors

Full Changelog: nodejs/undici@v7.24.7...v8.0.1

v8.0.0

Compare Source

What's Changed

Full Changelog: nodejs/undici@v7.24.7...v8.0.0

v7.26.0

Compare Source

What's Changed

Full Changelog: nodejs/undici@v7.25.0...v7.26.0

v7.25.0

Compare Source

What's Changed

Full Changelog: nodejs/undici@v7.24.8...v7.25.0

v7.24.8

Compare Source

What's Changed

Full Changelog: nodejs/undici@v7.24.7...v7.24.8

v7.24.7

Compare Source

What's Changed

New Contributors

Full Changelog: nodejs/undici@v7.24.6...v7.24.7

v7.24.6

Compare Source

What's Changed
New Contributors

Full Changelog: nodejs/undici@v7.24.5...v7.24.6

v7.24.5

Compare Source

What's Changed

New Contributors

Full Changelog: nodejs/undici@v7.24.4...v7.24.5

v7.24.4

Compare Source

What's Changed

Full Changelog: nodejs/undici@v7.24.3...v7.24.4

v7.24.3

Compare Source

What's Changed

  • fix(h2): TypeError: Cannot read properties of null (reading 'push') i… by @​hxinhan in #​4881

Full Changelog: nodejs/undici@v7.24.2...v7.24.3

v7.24.2

Compare Source

What's Changed

Full Changelog: nodejs/undici@v7.24.1...v7.24.2

v7.24.1

Compare Source

v7.24.0

Compare Source

What's Changed

Full Changelog: nodejs/undici@v7.23.0...v7.24.0

v7.23.0

Compare Source

v7.22.0

Compare Source

What's Changed

New Contributors

Full Changelog: nodejs/undici@v7.21.0...v7.22.0

v7.21.0

Compare Source

What's Changed

New Contributors

Full Changelog: nodejs/undici@v7.20.0...v7.21.0

v7.20.0

Compare Source

What's Changed

  • fix: preserve fetch stack traces b

Note

PR body was truncated to here.


Configuration

📅 Schedule: (in timezone Europe/Paris)

  • Branch creation
    • "after 7am every weekday,before 8pm every weekday"
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot requested a review from a team as a code owner April 24, 2026 09:44
@renovate
Copy link
Copy Markdown
Author

renovate Bot commented Apr 24, 2026

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: undefined
Post-upgrade command 'pre-commit autoupdate --freeze || true' has not been added to the allowed list in allowedCommands

@sonarqube-cloud-us
Copy link
Copy Markdown

@sonarqubecloud
Copy link
Copy Markdown

@sonar-review-alpha
Copy link
Copy Markdown

sonar-review-alpha Bot commented Apr 24, 2026

Summary

⚠️ The PR description exceeded the analysis limit and was truncated. The review may not reflect all context.

Dependency Update: Major Version Bumps

This PR updates three major dependencies that will need validation:

  • @actions/core ^1.11.1^3.0.0: Now ESM-only (breaking change from CommonJS)
  • typescript ^5.7.0^6.0.0: Major release with potential type checking changes
  • vitest ^3.0.0^4.0.0: Significant internal refactor (removed tinypool, debug, cac; restructured internal modules)

Good news: The codebase is already written in ESM (using import statements), so @actions/core's breaking change should not cause issues. The bundled output is created via ncc, which should handle ESM dependencies correctly.

What needs verification: Build artifacts, test execution, and runtime behavior of the bundled credential setup/guard scripts.

What reviewers should know

Review Focus

Start here: Verify the bundled outputs still work:

  • Run the build command (npm run build) and check that ncc successfully bundles with ESM @actions/core
  • Run tests (npm run test) to confirm vitest 4 compatibility with the existing test suite
  • TypeScript 6 may introduce new type errors—watch for tsc output if tests pass

Non-obvious changes:

  • @actions/core's transitive deps were also bumped significantly: @actions/exec (1.1.1 → 3.0.0), @actions/http-client (2.2.3 → 4.0.1), undici (5.29 → 6.25, dropping @fastify/busboy)
  • Vitest's internal module structure changed (es-module-lexer, chai, tinyrainbow versions); these may affect runtime behavior even though the test API surface is the same
  • No source code changes were needed—this is purely a dependency update, which is a good sign

Potential gotchas:

  • If ncc has issues bundling ESM modules, the build will fail (this would show up immediately in CI)
  • Check that the bundled dist/ directories are compatible with the GitHub Actions runner environment where they execute

  • Generate Walkthrough
  • Generate Diagram

🗣️ Give feedback

Copy link
Copy Markdown

@sonar-review-alpha sonar-review-alpha Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A couple of things need clarification before this can merge.

Registry split in package-lock.json: All 161 pre-existing packages in the lock file resolve from repox.jfrog.io (SonarSource's Artifactory proxy), but the 22 packages newly introduced by this upgrade resolve directly from registry.npmjs.org. If the Artifactory proxy exists for security scanning or to guarantee availability in restricted CI environments, those 22 packages are bypassing it. This looks like Renovate ran without the internal registry configured — worth confirming this is intentional or regenerating the lockfile with the proxy in place.

🗣️ Give feedback

Comment thread package-lock.json
"integrity": "sha512-hXJCSrkwfA46Vd9Z3q4cpEpHB1rL5NG04+/rbqW9d3+CSvtB1tYe8UTpAlixa1vj0m/ULglfEK2UKxMGxCxv5A==",
"version": "3.0.1",
"resolved": "https://registry.npmjs.org/@actions/core/-/core-3.0.1.tgz",
"integrity": "sha512-a6d/Nwahm9fliVGRhdhofo40HjHQasUPusmc7vBfyky+7Z+P2A1J68zyFVaNcEclc/Se+eO595oAr5nwEIoIUA==",
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All packages already in the lock file resolve from repox.jfrog.io, but every package newly added or replaced by this upgrade (here and in the @actions/exec, @actions/http-client, @actions/io, vitest ecosystem, and undici entries) resolves directly from registry.npmjs.org. If this Artifactory proxy is used for security scanning, licence checks, or to air-gap CI from the public registry, the 22 newly resolved packages are bypassing it.

This looks like Renovate generated the lockfile without the internal registry configured. Please regenerate with the proxy in place, or confirm this split is intentional.

  • Mark as noise

Comment thread package-lock.json
"version": "1.11.1",
"resolved": "https://repox.jfrog.io/artifactory/api/npm/npm/@actions/core/-/core-1.11.1.tgz",
"integrity": "sha512-hXJCSrkwfA46Vd9Z3q4cpEpHB1rL5NG04+/rbqW9d3+CSvtB1tYe8UTpAlixa1vj0m/ULglfEK2UKxMGxCxv5A==",
"version": "3.0.1",
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@actions/core v3.0.0 is ESM-only (the release notes explicitly state CommonJS consumers must switch to dynamic import()). The TypeScript source already uses ESM import syntax and ncc/esbuild handles ESM-to-CJS bundling, so the bundle itself should be fine. However, tsconfig.json sets "module": "commonjs" — TypeScript 6 has stricter module/resolution coupling and may fail to resolve types for ESM-only packages under the old node module resolution. Please confirm npm run build and tsc --noEmit both pass cleanly with this combination before merging.

  • Mark as noise

@renovate renovate Bot force-pushed the renovate/major-npm-dependencies branch from e4dc528 to 8016e22 Compare May 27, 2026 15:04
@renovate renovate Bot deployed to sca-checking May 27, 2026 15:04 Active
@sonarqubecloud
Copy link
Copy Markdown

@sonarqube-cloud-us
Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants