Skip to content

chore(deps): update dependency node to v26 - #1028

Merged
Danathar merged 1 commit into
mainfrom
renovate/node-26.x
Nov 17, 2026
Merged

Danathar merged 1 commit into
mainfrom
renovate/node-26.x

Conversation

@mergeraptor

@mergeraptor mergeraptor Bot commented Nov 16, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change Age Confidence
node uses-with major 24 → 26 age confidence
@types/node (source) devDependencies major 24.19.2 → 26.6.6 age confidence

Release Notes

actions/node-versions (node)

v26.13.1: 26.13.1

Compare Source

Node.js 26.13.1

v26.13.0: 26.13.0

Compare Source

Node.js 26.13.0

v26.12.1: 26.12.1

Compare Source

Node.js 26.12.1

v26.12.0: 26.12.0

Compare Source

Node.js 26.12.0

v26.11.1: 26.11.1

Compare Source

Node.js 26.11.1

v26.11.0: 26.11.0

Compare Source

Node.js 26.11.0

v26.10.0: 26.10.0

Compare Source

Node.js 26.10.0

v26.9.0: 26.9.0

Compare Source

Node.js 26.9.0

v26.8.2: 26.8.2

Compare Source

Node.js 26.8.2

v26.8.1: 26.8.1

Compare Source

Node.js 26.8.1

v26.8.0: 26.8.0

Compare Source

Node.js 26.8.0

v26.7.0: 26.7.0

Compare Source

Node.js 26.7.0

v26.6.0: 26.6.0

Compare Source

Node.js 26.6.0

v26.5.1: 26.5.1

Compare Source

Node.js 26.5.1

v26.5.0: 26.5.0

Compare Source

Node.js 26.5.0

v26.4.0: 26.4.0

Compare Source

Node.js 26.4.0

v26.3.1: 26.3.1

Compare Source

Node.js 26.3.1

v26.3.0: 26.3.0

Compare Source

Node.js 26.3.0

v26.2.0: 26.2.0

Compare Source

Node.js 26.2.0

v26.1.0: 26.1.0

Compare Source

Node.js 26.1.0

v26.0.0: 26.0.0

Compare Source

Node.js 26.0.0


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

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

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


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

This PR has been generated by Mend Renovate CLI.

@hivecommons-hive hivecommons-hive Bot added no-dco A commit is missing Signed-off-by — run `git rebase --signoff` role/trusted Author is trusted for unattended merge (trusted-author role or registry/claim tier in require_tiers) stage/050-review-pending Review swarm requested; awaiting a verdict for the current head labels Nov 16, 2026
@hivecommons-hive

Copy link
Copy Markdown
Contributor
991fb02

ℹ️ Sentinel notice — informational; author is trusted (allow-listed bot), merge is not blocked

Hive flagged this PR (author @mergeraptor[bot], head 991fb02ccbc7) because it matches behaviors that can override security controls, escalate privileges or damage the codebase. This is a heuristic, not an accusation — a maintainer should confirm the change is intended before it merges.

  • sensitive_path — changes 7 sensitive path(s) (Touches a sensitive path (OWNERS, workflows, policies, hive config, security docs, …))
    • .github/workflows/ci.yml
    • .github/workflows/copilot-setup-steps.yml
    • .github/workflows/deploy.yml
    • .github/workflows/preview.yml
    • .github/workflows/update-content.yml
    • package-lock.json
    • package.json

Hive did not add the sentinel-alert label because this author is trusted. The finding remains recorded for audit and the dashboard Security tab; set sentinel.trusted_authors_block: true to require the blocking label for trusted authors too.

@hivecommons-hive hivecommons-hive Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Summary: This update moves the website's automated build, test and deploy jobs from Node.js version 24 to version 26 (Node.js is the program that builds the site), and updates the matching type definitions. All the checks for this exact version passed, including the full test suite, type checks and the production build, so it looks safe to merge. One code comment still says the automated checks use version 24 and should be updated after this merges.


docs-currency (low, non-blocking)

  • vite.config.ts:46-48 and vite.config.ts:66-67 say the coverage figures were "Measured … on Node 24 (CI)". After this PR, CI runs Node 26 (.github/workflows/ci.yml:24, :70), so those comments name the wrong runtime. The test job passed at 991fb02 with --coverage (ci.yml:32), so the thresholds still hold on Node 26. Only the wording is stale. This bot regenerates the branch, so fix it on main after merge. Either re-measure on Node 26 and update the figures, or reword it to say "on Node 24 (CI at the time)".

What I checked: every setup-node step keeps its pinned SHA, and only node-version changed. No workflow other than images.yml calls setup-node, and images.yml never did. package.json has no engines field and the repo has no .nvmrc. The devcontainer installs Wolfi's unpinned nodejs package (.devcontainer/Containerfile:8). The lockfile entries for @types/node 26.6.6 and undici-types 8.9.0 resolve from registry.npmjs.org with integrity hashes. The CI checks test (lint, typecheck, tests with coverage, build), wolves-movie-flow, copilot-setup-steps and Audit GitHub Actions all succeeded on head 991fb02. deploy.yml and update-content.yml do not run on PRs, so Node 26 is not exercised there before merge. They run the same npm ci and build steps that CI covers.

No findings from: correctness, security, intent-alignment, style.

Confidence: 5/5 (safe)

— hive: agent=reviewer backend=claude model=claude-opus-5-5 effort=medium claude=2.1.325

@hivecommons-hive

Copy link
Copy Markdown
Contributor

Ready for a human merge: verdict approved @991fb02, 5/5 checks green, soak 30m0s elapsed. Blocked only by role/trusted.

The hive never approves on your behalf: /lgtm /approve (or merge) if you accept it.

@Danathar Danathar left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Approving. This moves CI, deploy and preview from Node 24 to Node 26 and bumps @types/node to match.

  • Node 26 has been the Active LTS line since 2026-10-28, and Node 24 is now in maintenance.
  • Node isn't pinned anywhere else (no .nvmrc or engines), and this updates every setup-node step.
  • Every dependency's Node floor is met: wrangler/miniflare >=22.12, vite ^20.19 or >=22.12.
  • CI is green on this head: lint, typecheck, tests with coverage, the production build and the wolves movie flow.

Small follow-up, not blocking: the coverage comments in vite.config.ts still say the figures were measured on Node 24.

@Danathar

Copy link
Copy Markdown
Contributor

Merging. Node goes from 24 to 26 in all five workflows that set it (CI, deploy, preview, update-content, copilot-setup-steps), and @types/node moves to match. The other lockfile changes come with that bump. CI built and checked the site on Node 26 at this head (5/5 green), it's approved on this head, and there is no hold. Adding it to the merge queue.

@Danathar
Danathar added this pull request to the merge queue Nov 17, 2026
Merged via the queue into main with commit 072d688 Nov 17, 2026
7 checks passed
@Danathar
Danathar deleted the renovate/node-26.x branch November 17, 2026 14:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

no-dco A commit is missing Signed-off-by — run `git rebase --signoff` role/trusted Author is trusted for unattended merge (trusted-author role or registry/claim tier in require_tiers) stage/050-review-pending Review swarm requested; awaiting a verdict for the current head

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant