Skip to content

chore: correct .nvmrc to v24 (MAPCO-11282) - #297

Merged
CL-SHLOMIKONCHA merged 1 commit into
masterfrom
fix/nvmrc-node-24
Aug 4, 2026
Merged

chore: correct .nvmrc to v24 (MAPCO-11282)#297
CL-SHLOMIKONCHA merged 1 commit into
masterfrom
fix/nvmrc-node-24

Conversation

@roicohen326

Copy link
Copy Markdown
Contributor

Summary

.nvmrc pins v12, but CI runs 24.x and master already depends on raster-shared@8.3.0-alpha.0, which declares engines: node>=24.

So nvm use && npm ci fails on master today:

npm ERR! notsup Unsupported engine for @map-colonies/raster-shared@8.3.0-alpha.0:
wanted {"node":">=24.0.0"} (current: {"node":"12.22.12"})

CI is unaffected — the workflows set node-version explicitly and never read .nvmrc. This is a local-development fix only.

The other five raster repos (overseer, job-tracker, ingestion-trigger, polygon-parts-worker, polygon-parts-manager) are all on v24 already; mc-models was missed.

No consumer impact — .nvmrc isn't published (files: ["Schema/**/*"]).

Unblocks local review of #296.

.nvmrc pinned v12 while CI (publish.yaml, pull_request.yaml) runs 24.x, and
master already depends on @map-colonies/raster-shared@8.3.0-alpha.0 which
declares engines node>=24.

Consequence: `nvm use && npm ci` fails today on master with
  npm ERR! notsup Unsupported engine for @map-colonies/raster-shared@8.3.0-alpha.0:
  wanted {"node":">=24.0.0"} (current: {"node":"12.22.12"})

CI is unaffected (it sets node-version explicitly and never reads .nvmrc), so
this is a local-development fix only. The other five raster repos in the
MAPCO-11282 sweep are all already on v24 — mc-models was missed.

.nvmrc is not published (files: ["Schema/**/*"]), so there is no consumer impact.
@CL-SHLOMIKONCHA
CL-SHLOMIKONCHA merged commit fd32209 into master Aug 4, 2026
5 checks passed
@CL-SHLOMIKONCHA
CL-SHLOMIKONCHA deleted the fix/nvmrc-node-24 branch August 4, 2026 10:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants