build(deps): bump actions/setup-node from 4 to 6#388
Closed
dependabot[bot] wants to merge 1 commit into
Closed
Conversation
Bumps [actions/setup-node](https://github.com/actions/setup-node) from 4 to 6. - [Release notes](https://github.com/actions/setup-node/releases) - [Commits](actions/setup-node@v4...v6) --- updated-dependencies: - dependency-name: actions/setup-node dependency-version: '6' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
dependabot
Bot
added
dependencies
3 tasks
kinyoklion
added a commit
that referenced
this pull request
Jul 6, 2026
…icy (#411) **Requirements** - [x] I have added test coverage for new or changed functionality (existing suite validates the build/runtime; this change is dev-tooling + config only) - [x] I have followed the repository's [pull request submission guidelines](../blob/main/CONTRIBUTING.md#submitting-pull-requests) - [x] I have validated my changes against all supported platform versions **Related issues** Replaces the currently open Dependabot PRs (#374, #377, #388, #392, #393, #394), all of which are major-version bumps. **Describe the solution you've provided** This consolidates dependency maintenance into a single, tested PR and codifies a safer Dependabot policy. 1. **Dependency update (`package.json`)** — bumps the `esbuild` devDependency `^0.24.0` → `^0.28.1` to resolve the moderate advisory GHSA-67mh-4wv8-2f99 (esbuild `<=0.24.2` dev server request). `npm audit` now reports **0 vulnerabilities**. esbuild `0.28.1` was released 2026-06-11 (~25 days ago), satisfying a 7-day quarantine. This is the only actionable update under the new same-major policy: `npm outdated` shows every other outstanding update is a major bump with no security justification, and everything else is already at the latest version within its current major. 2. **Dependabot policy (`.github/dependabot.yml`)** — for both the `npm` and `github-actions` ecosystems: - `cooldown: { default-days: 7 }` enforces the dependency quarantine (only adopt releases ≥7 days old) going forward. - `ignore` on `dependency-name: "*"` with `update-types: ["version-update:semver-major"]` restricts version-update PRs to the current major. Per GitHub's docs, `update-types` does not affect security updates, so Dependabot will still open a major-version PR when required to resolve a vulnerability. Validated locally: `npm run build`, `npm run lint`, `tsc`, and the full `jest` suite (93 tests) all pass, and `npm audit` is clean. **Describe alternatives you've considered** - Adopting the open React 19 devDependency bumps (react, react-dom, react-test-renderer and their `@types`) and `actions/setup-node` v6. These are all major bumps with no security driver, so they are intentionally excluded under the new same-major policy. They can be pursued separately as deliberate, tested major upgrades if desired. - A global `semver-major` ignore alone (without noting the security exemption): documented behavior confirms security updates are unaffected by `update-types`, so the security-major path remains open. **Additional context** The 7-day quarantine and same-major restriction reduce exposure to supply-chain risk from freshly published or major releases while keeping security fixes flowing. Link to Devin session: https://app.devin.ai/sessions/9a6e6afb929646c3b9d14c4f13a17601 Requested by: @kinyoklion <!-- CURSOR_SUMMARY --> --- > [!NOTE] > **Low Risk** > DevDependency and Dependabot config only; no changes to the published SDK runtime or consumer-facing APIs. > > **Overview** > Bumps the **esbuild** devDependency from `^0.24.0` to `^0.28.1` to address moderate advisory GHSA-67mh-4wv8-2f99 (dev-server request handling in older esbuild). This is a build-time-only change. > > Updates **`.github/dependabot.yml`** for both **npm** and **github-actions**: documents the existing 7-day **cooldown** quarantine and adds a global **`ignore`** for **`version-update:semver-major`**, so routine Dependabot PRs stay on the current major. Security-driven updates can still propose major bumps per GitHub’s rules. > > <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit 503cc1f. Bugbot is set up for automated code reviews on this repo. Configure [here](https://www.cursor.com/dashboard/bugbot).</sup> <!-- /CURSOR_SUMMARY --> --------- Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
Contributor
Author
|
Looks like actions/setup-node is no longer being updated by Dependabot, so this is no longer needed. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps actions/setup-node from 4 to 6.
Release notes
Sourced from actions/setup-node's releases.
... (truncated)
Commits
48b55a0Update Node.js versions in versions.yml and bump package to v6.4.0 (#1533)ab72c7eUpgrade@actionsdependencies (#1525)53b8394Bump minimatch from 3.1.2 to 3.1.5 (#1498)54045abScope test lockfiles by package manager and update cache tests (#1495)c882bffReplace uuid with crypto.randomUUID() (#1378)774c1d6feat(node-version-file): support parsingdevEnginesfield (#1283)efcb663fix: remove hardcoded bearer (#1467)d02c89dFix npm audit issues (#1491)6044e13Docs: bump actions/checkout from v5 to v6 (#1468)8e49463Fix README typo (#1226)You can trigger a rebase of this PR by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)Note
Low Risk
Low risk workflow-only change that updates the Node setup GitHub Action; potential impact is limited to CI/publish runs if
setup-node@v6behavior differs (e.g., caching defaults).Overview
Updates GitHub Actions workflows to use
actions/setup-node@v6instead of@v4across CI, docs publishing, and release/publish pipelines.No application/runtime code changes; the main effect is altered CI environment setup during builds, tests, and publish steps.
Reviewed by Cursor Bugbot for commit 7f2486b. Bugbot is set up for automated code reviews on this repo. Configure here.