---
title: "corestack_node_version_change"
url: https://docs.corefinity.com/mcp/tools/corestack_node_version_change
type: tool
last_updated: 2026-11-13
feature: node-runtime
related:
  - https://docs.corefinity.com/api/reference/runtime/update-node-runtime.md
  - https://docs.corefinity.com/guides/sites/software-and-services/node-js.md
---
# corestack_node_version_change

**Change the Node.js version.** Move a row to another Node.js major from corestack_node_runtime_get's options, at its `revision`, now or tonight. Its global packages are reinstalled for the new major at their pinned versions. A major the row needs acknowledged is refused with ack_required naming it. Scope: write. Long-running: answers with a task.

- Scope: `write`
- Runs as a task: yes

## When to use it

Move a row to another Node.js major from corestack_node_runtime_get's `options`, at its `revision`, now or tonight. The global packages are reinstalled for the new major at their pinned versions. A row already on the new runtime changes straight away; a row not yet on it moves to it with this change. Leaving Node.js 16, `keep_legacy_tools` (default true) keeps gulp, grunt-cli, sass and magepack as global packages. The task follows the change; a refused install ends `work_failed` and the previous version keeps running.

## Inputs

- `site_id` (integer, ≥ 1, required)
- `revision` (integer, ≥ 0, required): from corestack_node_runtime_get.
- `major` (integer, required): e.g. 24.
- `acknowledge` (array of `eol`): only after `ack_required` and telling the person.
- `keep_legacy_tools` (boolean)
- `apply` (`now` or `tonight`)

### Input schema

```json
{
  "additionalProperties": false,
  "properties": {
    "acknowledge": {
      "description": "What ack_required named, once you have told the person.",
      "items": {
        "enum": [
          "eol"
        ],
        "type": "string"
      },
      "maxItems": 1,
      "type": "array"
    },
    "apply": {
      "default": "now",
      "description": "now, or tonight in the row's maintenance window. window: the row's next maintenance window (tonight is kept as its alias).",
      "enum": [
        "now",
        "window",
        "tonight"
      ],
      "type": "string"
    },
    "keep_legacy_tools": {
      "default": true,
      "description": "Leaving Node.js 16: keep gulp, grunt-cli, sass and magepack as global packages.",
      "type": "boolean"
    },
    "major": {
      "description": "The Node.js major, e.g. 24.",
      "maximum": 99,
      "minimum": 1,
      "type": "integer"
    },
    "revision": {
      "description": "From corestack_node_runtime_get; stale when the row changed since.",
      "minimum": 0,
      "type": "integer"
    },
    "site_id": {
      "description": "The row: the site or one of its environments.",
      "minimum": 1,
      "type": "integer"
    }
  },
  "required": [
    "site_id",
    "revision",
    "major"
  ],
  "type": "object"
}
```

## Refusals

- `ack_required`: an end-of-life major; tell the person, then send `acknowledge: ["eol"]`.
- `node_major_existing_only`, `node_platform_minimum`, `node_major_unavailable`: not a major this row may move to.
- `stale`: the row changed since you read it; read it again.
- `runtime_locked`: Corefinity has locked this row's Node.js settings.
- `busy`, `change_pending`: another change is running or queued.
- `runtime_not_adopted`: the row cannot move to the new runtime yet; `details.adoption` says why.
- `feature_off` on `apply`: tonight's changes are switched off.
- `managed_elsewhere` (message: "This site is managed by another control panel"): another control panel manages this site, so use that control panel for it. This is refused before anything else about the site, as in the Control Panel and the API. Nothing was done.
- The refusals every tool can answer: `invalid_arguments`, `tenant_mismatch`, `scope_required`, `pin_refused`, `rate_limited`, `temporarily_unavailable`, `internal_error` (corestack://guides/how-this-server-works).

## Example

```json
{
  "name": "corestack_node_version_change",
  "arguments": {
    "site_id": 4211,
    "revision": 7,
    "major": 24
  }
}
```

## Prompt

```text
Using the Corefinity MCP server, call corestack_node_version_change with site_id 4211, revision 7, major 24. (Change the Node.js version.) Tell me what it returned.
```

## The same task elsewhere

- Endpoint: [PUT /api/corestack/sites/{site}/node-runtime](https://docs.corefinity.com/api/reference/runtime/update-node-runtime.md)
- Guide: [Node.js configuration](https://docs.corefinity.com/guides/sites/software-and-services/node-js.md)
