chore(dev-base): reconcile mcporter Node 24 engine requirement #814

Open
opened 2026-07-30 12:35:16 +00:00 by coilyco-ops · 1 comment
Member

The local dev-base build warns that mcporter 0.12.3 declares Node >=24 while the shared image remains on the supported Node 22 major. The command still verifies successfully, but the image should not carry a persistent EBADENGINE warning. Decide whether to advance the shared runtime to Node 24 or pin a compatible mcporter release, then verify every language tier and the full fan-in image without the warning. This was discovered while validating #813 and is intentionally separate from that patch because a Node major upgrade needs its own compatibility review.

The local dev-base build warns that mcporter 0.12.3 declares Node >=24 while the shared image remains on the supported Node 22 major. The command still verifies successfully, but the image should not carry a persistent EBADENGINE warning. Decide whether to advance the shared runtime to Node 24 or pin a compatible mcporter release, then verify every language tier and the full fan-in image without the warning. This was discovered while validating #813 and is intentionally separate from that patch because a Node major upgrade needs its own compatibility review.
Author
Member

Fresh evidence from dev-base PR run 2743 on 2026-08-04:

  • The full image uses Node 22.23.2.
  • Installing mcporter 0.12.3 emits EBADENGINE because the package declares Node 24 or newer.
  • mcporter help verification still passes and the complete image build is green.

PR #866 intentionally leaves Node unchanged so full-only tool updates reuse the language cache. This issue remains the correct separate compatibility decision because either path changes a language/runtime contract.

Fresh evidence from dev-base PR run 2743 on 2026-08-04: * The full image uses Node 22.23.2. * Installing mcporter 0.12.3 emits EBADENGINE because the package declares Node 24 or newer. * mcporter help verification still passes and the complete image build is green. PR #866 intentionally leaves Node unchanged so full-only tool updates reuse the language cache. This issue remains the correct separate compatibility decision because either path changes a language/runtime contract.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
coilyco-flight-deck/agentic-os#814
No description provided.