[ferrlabs-renovate]

This PR contains the following updates:

Package	Type	Update	Change
node	uses-with	major	24 → 26

---

Release Notes

actions/node-versions (node)

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
  • "before 6am on monday"
• 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 has been generated by Mend Renovate CLI.

[ferrfleet-interne]

Only change: node-version 24 to 26 for the npm publish job in mcp-publish.yml. This is the only setup-node use in the repo's workflows.

What matters here: mcp/package.json has engines.node >=22.0.0, so 26 is allowed. The job only runs pnpm install, pnpm build, pnpm pack and npm@11 publish, with no APIs tied to a Node major. I did not read the Node 26 release notes line by line, so a breaking change in a tool the build uses is possible but unlikely. The job runs only on release or manual dispatch, so no PR check exercises it. At the time of review CI was still running, with nothing failed.

Nit: mcp/Dockerfile:4 and mcp/Dockerfile:15 still use node:24-alpine. After this merge the npm package is built on 26 and the GHCR image on 24. That is harmless, but you may want the two to match. Renovate won't bump the Dockerfile as part of this PR.