Skip to content

fix(staging): pin engines.node to exact 22.23.4 for CF buildpack compatibility - #2961

Merged
jung-thomas merged 1 commit into
DEVfrom
fix/node-engine-pin-exact
Nov 1, 2026
Merged

jung-thomas merged 1 commit into
DEVfrom
fix/node-engine-pin-exact

Conversation

@jung-thomas

Copy link
Copy Markdown
Contributor

Summary

  • CF nodejs_buildpack v1.9.6 rejects compound semver ranges like >=22.23.4 <23 with "improper constraint" — it only accepts 22.x or exact versions
  • The >=22.23.4 <23 range introduced by the CVE-2026-111497 fix caused BuildpackCompileFailed on all three deployed modules during the 2026-11-01 DEV deploy
  • Changed all three package.json files to exact pin 22.23.4, which satisfies the CVE floor and is accepted by the buildpack resolver

Files changed: package.json, srv-qa/package.json, srv-mcp/package.json

Test plan

  • Deploy to DEV passes tutorials-srv staging (was failing with Unable to install node: improper constraint: >=22.23.4 <23)
  • Verify cf app tutorials-srv shows Node 22.23.4 post-deploy
  • No regression on srv-qa or MCP modules

…atibility

CF nodejs_buildpack v1.9.6 rejects compound semver ranges (>=x.y.z <n)
with "improper constraint" — it only accepts simple ranges like 22.x or
exact versions. The >=22.23.4 <23 range (set in the CVE-2026-111497 fix)
caused BuildpackCompileFailed on all three deployed modules during the
2026-11-01 DEV deploy.

Exact pin 22.23.4 satisfies the CVE floor requirement and is accepted by
the buildpack resolver. Updated: package.json, srv-qa/package.json,
srv-mcp/package.json.
@jung-thomas
jung-thomas merged commit a370db1 into DEV Nov 1, 2026
7 checks passed
@jung-thomas
jung-thomas deleted the fix/node-engine-pin-exact branch November 1, 2026 10:22
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.

1 participant