corestack_ node_ follow_ repository_ set
Follow the repository's Node.js version.
When to use it
Turn follow mode on or off at the row's revision. With it on, each deployment switches the row to the Node.js major its repository asks for (.nvmrc, engines.node and the like) when that major is offered and supported, never an end-of-life one. Only the switch changes.
Ask for it
Using the Corefinity MCP server, call corestack_node_follow_repository_set with site_id 4211, revision 7, enabled true. (Follow the repository's Node.js version.) Tell me what it returned.Inputs
enabledbooleanRequired
true to follow the repository, false to keep the chosen major.
revisionintegerRequired
From corestack_node_runtime_get; stale when the row changed since. At least 0.
site_idintegerRequired
The row: the site or one of its environments. At least 1.
Example call
{
"name": "corestack_node_follow_repository_set",
"arguments": {
"site_id": 4211,
"revision": 7,
"enabled": true
}
}If it is refused
| Reason | What to do |
|---|---|
runtime_not_adopted | The row is not on the new runtime yet. |
stale | runtime_locked: as corestack_node_version_change. |
managed_elsewhere | 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. |
invalid_arguments | The arguments do not match the tool's input schema, or the Control Panel refused a field. Fix the fields named in the answer and call again. |
tenant_mismatch | The object does not exist or the token may not see it. Check the id. |
scope_required | The token lacks a scope this call needs. Open the link in the answer to add it, then call again. |
pin_refused | The grant is limited to chosen clusters, sites or environments, and this call is outside them. Open the link in the answer to widen it. |
rate_limited | Too many calls. Wait for the number of seconds the answer names. |
temporarily_unavailable | The Control Panel could not answer just now. Nothing was started; try again shortly. |
internal_error | Something went wrong on our side. Quote the trace id to support. |
The same task elsewhere
Was this helpful?