Example:
prisma/prisma-engines#2208 (original)
prisma/prisma-engines#2196 (copy in our repo)
https://buildkite.com/prisma/release-prisma-engines/builds/1596
https://github.com/prisma/engines-wrapper/actions/runs/1197982488
https://github.com/prisma/engines-wrapper/runs/3506044105?check_suite_focus=true
b112a3a
2.31.0-25.node-api-threadsafe-unref-1ca259332bad49e28dd3eda822c358a766b3ec08

See how the GH Actions run skips the Workflow dispatch to prisma/prisma for version update step. One way this is great, as it does not automatically create a new dev version. On the other hand we do not get an automatic version with this engine.

Should maybe auto create an integration branch of the same name and open a PR? (via triggering a special version of the workflow on prisma/prisma)

Right now, this repository is falling behind in terms of eslint, typescript, and esbuild configs. It would be great to maintain this from a single place, ideally shipped as a package from prisma/prisma.

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• Update dependency @types/node to v18.19.44
• Update dependencies (major) (major) (@sindresorhus/slugify, chalk, execa, husky, node-fetch, prettier, typescript)

Ignored or Blocked

These are blocked by an existing closed PR and will not be recreated unless you click a checkbox below.

• Update dependency @types/node to v20

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

Bug description

Some modules cannot be upgraded because they use ESM syntax. In turn, our tests fail.

How to reproduce

For example see #131

Expected behavior

We should be able to run the tests since we are able to compile ES modules.

The goal of this is to have a clean architecture where prisma/prisma depends on prisma/engines-wrapper. At the moment prisma/prisma depends on prisma/engines-wrapper that depends on prisma/prisma through @prisma/debug.

To avoid maintenance burden, instead of separating it into another repo, we could change our publish script to only publish to only publish (ie. @prisma/debug) if it has changes to be published. We can also argue that @prisma/debug is a tool that does not even depend on the engines an is thus not subject to the same versioning. This could be the opportunity to set up a new repo for tools and manage it perhaps via changesets.

Context https://prisma-company.slack.com/archives/CUXLS0Z6K/p1631084401029500

https://prisma-company.slack.com/archives/CUXLS0Z6K/p1629973675002700

In https://github.com/prisma/engines-wrapper/blob/main/.github/workflows/publish-engines.yml we receive a payload, and use that to update a dependency in this repo, then publish a new version to Npm. That Npm package version is not really visible here, but would make it easier to find stuff when debugging problems.

Possibilities:

• Tag commit with Npm version (after it was actually published)
• Add npm version to commit message (before the publish happened)
• ...

Similar to prisma/prisma: https://github.com/prisma/prisma/search?q=codecov

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

File: renovate.json
Error type: Invalid JSON (parsing failed)
Message: Syntax error: expecting String near uke4"], }

The action receives a payload, but does not really make it visible in a simple way.

You can see it when you know where to look:

i am getting the below error, when tried npx prisma generate

Error: Unknown binaryTarget debian-openssl-3.0.x and no custom binaries were provided

node version: v16.17.0
@prisma/client version: 3.13.0
openssl version: OpenSSL 3.0.2 15 Mar 2022 (Library: OpenSSL 3.0.2 15 Mar 2022)

i also tried by adding this line binaryTargets = ["native", "debian-openssl-3.0.x"] to schema.prisma. but getting the same error.

-- note: tried reinstalling the node_modules and also installed the @prisma/client version > 4.x.x

All the content in this repo depends closely on the engines commit that they are using. We should add the commit hash and also a link to prisma-engines with that commit to the README.

https://github.com/prisma/engines-wrapper/tree/main/packages/engines-version doesn't have any test

It would be better to have some test, so we can safely merge Renovate PRs like #240

See #240