Fix engines.node: >=18 → 18.x for Heroku compatibility#421
Merged
Conversation
Heroku rejects semver ranges with the >= operator. 18.x is equivalent and accepted by Heroku's Node.js buildpack.
Member
|
[diff-counting] Significant lines: 0. |
CasperL1218
requested review from
BryanGraeser,
Natk21,
NigelTatem and
bryanshao07
and removed request for
BryanGraeser
laurenp-2
approved these changes
Apr 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
engines.nodefrom>=18to18.x— Heroku rejects the>=operator in the engines fieldTest Plan
Redeploy to
cuapts-stagingafter merge — build should succeed.Notes
>=18was introduced in the previous PR (#418).18.xis equivalent and accepted by Heroku's Node.js buildpack.