Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(ci): node 22 #1982

Merged
merged 23 commits into from
Jun 15, 2024
Merged

feat(ci): node 22 #1982

merged 23 commits into from
Jun 15, 2024

Conversation

DerekRoberts
Copy link
Member

@DerekRoberts DerekRoberts commented May 22, 2024

Closes #1966


Thanks for the PR!

Deployments, as required, will be available below:

Please create PRs in draft mode. Mark as ready to enable:

After merge, new images are deployed in:


Thanks for the PR!

Deployments, as required, will be available below:

Please create PRs in draft mode. Mark as ready to enable:

After merge, new images are deployed in:

@DerekRoberts DerekRoberts marked this pull request as ready for review May 22, 2024 04:37
@DerekRoberts DerekRoberts self-assigned this May 22, 2024
@DerekRoberts DerekRoberts added enhancement New feature or request dependencies Pull requests that update a dependency file labels May 22, 2024
@DerekRoberts DerekRoberts reopened this May 22, 2024
@DerekRoberts DerekRoberts force-pushed the feat/ci/node22 branch 2 times, most recently from 2d997f6 to ef82dc4 Compare June 3, 2024 19:38
@DerekRoberts DerekRoberts force-pushed the feat/ci/node22 branch 2 times, most recently from c34b417 to 876111b Compare June 13, 2024 20:40
@mishraomp
Copy link
Collaborator

now after deployment we are getting

PrismaClientInitializationError: Prisma Client could not locate the Query Engine for runtime "debian-openssl-3.0.x".

This happened because Prisma Client was generated for "debian-openssl-1.1.x", but the actual deployment required "debian-openssl-3.0.x".
Add "debian-openssl-3.0.x" to `binaryTargets` in the "schema.prisma" file and run `prisma generate` after saving it:

generator client {
  provider      = "prisma-client-js"
  binaryTargets = ["native", "debian-openssl-3.0.x"]
}

The following locations have been searched:
  /app/node_modules/.prisma/client
  /app/node_modules/@prisma/client
  /tmp/prisma-engines
    at wa (/app/node_modules/@prisma/client/runtime/library.js:64:805)
    at async Object.loadLibrary (/app/node_modules/@prisma/client/runtime/library.js:111:10060)
    at async wt.loadEngine (/app/node_modules/@prisma/client/runtime/library.js:112:448)
    at async wt.instantiateLibrary (/app/node_modules/@prisma/client/runtime/library.js:111:12829) {
  clientVersion: '5.15.0',
  errorCode: undefined
}

Node.js v22.3.0

will look into it @DerekRoberts

@DerekRoberts
Copy link
Member Author

@mishraomp All good. Thanks for staying on top of this. :)

@mishraomp
Copy link
Collaborator

all set @DerekRoberts :)

Copy link
Collaborator

@mishraomp mishraomp left a comment

Choose a reason for hiding this comment

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

Node 22, 😍

@DerekRoberts DerekRoberts merged commit f7c40d7 into main Jun 15, 2024
24 checks passed
@DerekRoberts DerekRoberts deleted the feat/ci/node22 branch June 15, 2024 03:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file enhancement New feature or request
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

Support Node.js version 22
2 participants