Skip to content

Conversation

@Sajito
Copy link
Contributor

@Sajito Sajito commented Nov 20, 2025

The current configuration prevents consumers from using higher node versions, while having strict-engine checks enabled.
Higher node versions might not be officially supported, but I think they shouldn't be blocked, unless they are known to now work.

Resolves #28594

@CLAassistant
Copy link

CLAassistant commented Nov 20, 2025

CLA assistant check
All committers have signed the CLA.

Copy link
Member

@aqrln aqrln left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you!

@dosubot dosubot bot added the lgtm This PR has been approved by a maintainer label Nov 21, 2025
@aqrln aqrln added this to the 7.1.0 milestone Nov 21, 2025
@jkomyno jkomyno modified the milestones: 7.1.0, 7.0.1 Nov 24, 2025
@jkomyno jkomyno merged commit 3230645 into prisma:main Nov 24, 2025
179 checks passed
jkomyno pushed a commit that referenced this pull request Nov 25, 2025
The current configuration prevents consumers from using higher node
versions, while having strict-engine checks enabled.
Higher node versions might not be officially supported, but I think they
shouldn't be blocked, unless they are known to now work.

Resolves #28594
jkomyno pushed a commit that referenced this pull request Nov 25, 2025
The current configuration prevents consumers from using higher node
versions, while having strict-engine checks enabled.
Higher node versions might not be officially supported, but I think they
shouldn't be blocked, unless they are known to now work.

Resolves #28594
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

lgtm This PR has been approved by a maintainer

Projects

None yet

Development

Successfully merging this pull request may close these issues.

NodeJS 25 not working

5 participants