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

chore(deps): update e2e tests (major) #23143

Closed
wants to merge 1 commit into from
Closed

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 15, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence Type Update
@​prisma/extension-accelerate 0.6.3 -> 1.0.0 age adoption passing confidence dependencies major
@types/node (source) 16.18.96 -> 20.12.7 age adoption passing confidence devDependencies major
@types/node (source) 16.18.96 -> 20.12.7 age adoption passing confidence devDependencies major
@types/node (source) 16.18.96 -> 20.12.7 age adoption passing confidence devDependencies major
@types/node (source) 16.18.96 -> 20.12.7 age adoption passing confidence devDependencies major
@types/node (source) 16.18.96 -> 20.12.7 age adoption passing confidence devDependencies major
@types/node (source) 18.19.31 -> 20.12.7 age adoption passing confidence devDependencies major
@types/node (source) 16.18.96 -> 20.12.7 age adoption passing confidence devDependencies major
node 18 -> 20 age adoption passing confidence final major
vercel (source) 33.5.0 -> 33.7.1 age adoption passing confidence dependencies major

Release Notes

nodejs/node (node)

v20.12.2: 2024-04-10, Version 20.12.2 'Iron' (LTS), @​RafaelGSS

Compare Source

This is a security release.

Notable Changes
  • CVE-2024-27980 - Command injection via args parameter of child_process.spawn without shell option enabled on Windows
Commits

v20.12.1: 2024-04-03, Version 20.12.1 'Iron' (LTS), @​RafaelGSS

Compare Source

This is a security release

Notable Changes
  • CVE-2024-27983 - Assertion failed in node::http2::Http2Session::~Http2Session() leads to HTTP/2 server crash- (High)
  • CVE-2024-27982 - HTTP Request Smuggling via Content Length Obfuscation - (Medium)
  • llhttp version 9.2.1
  • undici version 5.28.4
Commits

v20.12.0: 2024-03-26, Version 20.12.0 'Iron' (LTS), @​richardlau

Compare Source

Notable Changes
crypto: implement crypto.hash()

This patch introduces a helper crypto.hash() that computes
a digest from the input at one shot. This can be 1.2-2x faster
than the object-based createHash() for smaller inputs (<= 5MB)
that are readily available (not streamed) and incur less memory
overhead since no intermediate objects will be created.

const crypto = require('node:crypto');

// Hashing a string and return the result as a hex-encoded string.
const string = 'Node.js';
// 10b3493287f831e81a438811a1ffba01f8cec4b7
console.log(crypto.hash('sha1', string));

Contributed by Joyee Cheung in #​51044.

Loading and parsing environment variables
  • process.loadEnvFile(path):

    • Use this function to load the .env file. If no path is specified, it automatically loads the .env file in the current directory. Example: process.loadEnvFile().
    • Load a specific .env file by specifying its path. Example: process.loadEnvFile('./development.env').
  • util.parseEnv(content):

    • Use this function to parse an existing string containing environment variable assignments.
    • Example usage: require('node:util').parseEnv('HELLO=world').

Contributed by Yagiz Nizipli in #​51476.

New connection attempt events

Three new events were added in the net.createConnection flow:

  • connectionAttempt: Emitted when a new connection attempt is established. In case of Happy Eyeballs, this might emitted multiple times.
  • connectionAttemptFailed: Emitted when a connection attempt failed. In case of Happy Eyeballs, this might emitted multiple times.
  • connectionAttemptTimeout: Emitted when a connection attempt timed out. In case of Happy Eyeballs, this will not be emitted for the last attempt. This is not emitted at all if Happy Eyeballs is not used.

Additionally, a previous bug has been fixed where a new connection attempt could have been started after a previous one failed and after the connection was destroyed by the user.
This led to a failed assertion.

Contributed by Paolo Insogna in #​51045.

Permission Model changes

Node.js 20.12.0 comes with several fixes for the experimental permission model and two new semver-minor commits.
We're adding a new flag --allow-addons to enable addon usage when using the Permission Model.

$ node --experimental-permission --allow-addons

Contributed by Rafael Gonzaga in #​51183

And relative paths are now supported through the --allow-fs-* flags.
Therefore, with this release one can use:

$ node --experimental-permission --allow-fs-read=./index.js

To give only read access to the entrypoint of the application.

Contributed by Rafael Gonzaga and Carlos Espa in #​50758.

sea: support embedding assets

Users can now include assets by adding a key-path dictionary
to the configuration as the assets field. At build time, Node.js
would read the assets from the specified paths and bundle them into
the preparation blob. In the generated executable, users can retrieve
the assets using the sea.getAsset() and sea.getAssetAsBlob() API.

{
  "main": "/path/to/bundled/script.js",
  "output": "/path/to/write/the/generated/blob.blob",
  "assets": {
    "a.jpg": "/path/to/a.jpg",
    "b.txt": "/path/to/b.txt"
  }
}

The single-executable application can access the assets as follows:

const { getAsset } = require('node:sea');
// Returns a copy of the data in an ArrayBuffer
const image = getAsset('a.jpg');
// Returns a string decoded from the asset as UTF8.
const text = getAsset('b.txt', 'utf8');
// Returns a Blob containing the asset without copying.
const blob = getAssetAsBlob('a.jpg');

Contributed by Joyee Cheung in #​50960.

Support configurable snapshot through --build-snapshot-config flag

We are adding a new flag --build-snapshot-config to configure snapshots through a custom JSON configuration file.

$ node --build-snapshot-config=/path/to/myconfig.json

When using this flag, additional script files provided on the command line will
not be executed and instead be interpreted as regular command line arguments.

These changes were contributed by Joyee Cheung and Anna Henningsen in #​50453

Text Styling
  • util.styleText(format, text): This function returns a formatted text considering the format passed.

A new API has been created to format text based on util.inspect.colors, enabling you to style text in different colors (such as red, blue, ...) and emphasis (italic, bold, ...).

const { styleText } = require('node:util');
const errorMessage = styleText('red', 'Error! Error!');
console.log(errorMessage);

Contributed by Rafael Gonzaga in #​51850.

vm: support using the default loader to handle dynamic import()

This patch adds support for using vm.constants.USE_MAIN_CONTEXT_DEFAULT_LOADER as the
importModuleDynamically option in all vm APIs that take this option except vm.SourceTextModule. This allows users to have a shortcut to support dynamic import() in the compiled code without missing the compilation cache if they don't need customization of the loading process. We emit an experimental warning when the import() is actually handled by the default loader through this option instead of requiring --experimental-vm-modules.

const { Script, constants } = require('node:vm');
const { resolve } = require('node:path');
const { writeFileSync } = require('node:fs');

// Write test.js and test.txt to the directory where the current script
// being run is located.
writeFileSync(resolve(__dirname, 'test.mjs'),
              'export const filename = "./test.json";');
writeFileSync(resolve(__dirname, 'test.json'),
              '{"hello": "world"}');

// Compile a script that loads test.mjs and then test.json
// as if the script is placed in the same directory.
const script = new Script(
  `(async function() {
    const { filename } = await import('./test.mjs');
    return import(filename, { with: { type: 'json' } })
  })();`,
  {
    filename: resolve(__dirname, 'test-with-default.js'),
    importModuleDynamically: constants.USE_MAIN_CONTEXT_DEFAULT_LOADER,
  });

// { default: { hello: 'world' } }
script.runInThisContext().then(console.log);

Contributed by Joyee Cheung in #​51244.

Root certificates updated to NSS 3.98

Certificates added:

  • Telekom Security TLS ECC Root 2020
  • Telekom Security TLS RSA Root 2023

Certificates removed:

  • Security Communication Root CA
Updated dependencies
  • acorn updated to 8.11.3.
  • ada updated to 2.7.6.
  • base64 updated to 0.5.2.
  • brotli updated to 1.1.0.
  • c-ares updated to 1.27.0.
  • corepack updated to 0.25.2.
  • ICU updated to 74.2. Includes CLDR 44.1 and Unicode 15.1.
  • nghttp2 updated to 1.60.0.
  • npm updated to 10.5.0. Fixes a regression in signals not being passed onto child processes.
  • simdutf8 updated to 4.0.8.
  • Timezone updated to 2024a.
  • zlib updated to 1.3.0.1-motley-40e35a7.
Other notable changes
Commits

Configuration

📅 Schedule: Branch creation - "before 7am on Wednesday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot requested a review from a team as a code owner February 15, 2024 01:01
@renovate renovate bot requested review from SevInf, Druue, aqrln, jkomyno, Jolg42 and millsp and removed request for a team February 15, 2024 01:01
Copy link
Contributor Author

renovate bot commented Feb 15, 2024

⚠ Artifact update problem

Renovate failed to update artifacts related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: packages/client/tests/e2e/prisma-client-imports/pnpm-lock.yaml
undefined
 ENOENT  ENOENT: no such file or directory, open '/tmp/prisma-0.0.0.tgz'

This error happened while installing a direct dependency of /tmp/renovate/repos/github/prisma/prisma/packages/client/tests/e2e/prisma-client-imports



.                                        |  WARN  Installing a dependency from a non-existent directory: /tmp/renovate/repos/github/prisma/prisma/packages/client/tests/e2e/prisma-client-imports/custom

File name: packages/client/tests/e2e/unsupported-edge-error/pnpm-lock.yaml
undefined
 ENOENT  ENOENT: no such file or directory, open '/tmp/prisma-0.0.0.tgz'

This error happened while installing a direct dependency of /tmp/renovate/repos/github/prisma/prisma/packages/client/tests/e2e/unsupported-edge-error



Progress: resolved 1, reused 0, downloaded 0, added 0

File name: packages/client/tests/e2e/unsupported-browser-error/pnpm-lock.yaml
undefined
 ENOENT  ENOENT: no such file or directory, open '/tmp/prisma-0.0.0.tgz'

This error happened while installing a direct dependency of /tmp/renovate/repos/github/prisma/prisma/packages/client/tests/e2e/unsupported-browser-error




File name: packages/client/tests/e2e/schema-not-found-sst-electron/pnpm-lock.yaml
undefined
 ENOENT  ENOENT: no such file or directory, open '/tmp/prisma-0.0.0.tgz'

This error happened while installing a direct dependency of /tmp/renovate/repos/github/prisma/prisma/packages/client/tests/e2e/schema-not-found-sst-electron




File name: packages/client/tests/e2e/require-in-the-middle/pnpm-lock.yaml
undefined
 ENOENT  ENOENT: no such file or directory, open '/tmp/prisma-0.0.0.tgz'

This error happened while installing a direct dependency of /tmp/renovate/repos/github/prisma/prisma/packages/client/tests/e2e/require-in-the-middle




File name: packages/client/tests/e2e/publish-extensions/pnpm-lock.yaml
undefined
 ENOENT  ENOENT: no such file or directory, open '/tmp/prisma-0.0.0.tgz'

This error happened while installing a direct dependency of /tmp/renovate/repos/github/prisma/prisma/packages/client/tests/e2e/publish-extensions




File name: packages/client/tests/e2e/pg-self-signed-cert-error/pnpm-lock.yaml
undefined
 ENOENT  ENOENT: no such file or directory, open '/tmp/prisma-0.0.0.tgz'

This error happened while installing a direct dependency of /tmp/renovate/repos/github/prisma/prisma/packages/client/tests/e2e/pg-self-signed-cert-error



Progress: resolved 1, reused 0, downloaded 0, added 0

File name: packages/client/tests/e2e/noengine-file-deletion/pnpm-lock.yaml
undefined
 ENOENT  ENOENT: no such file or directory, open '/tmp/prisma-0.0.0.tgz'

This error happened while installing a direct dependency of /tmp/renovate/repos/github/prisma/prisma/packages/client/tests/e2e/noengine-file-deletion




File name: packages/client/tests/e2e/nextjs-schema-not-found/9_monorepo-noServerComponents-customOutput-noReExport/pnpm-lock.yaml
/tmp/renovate/repos/github/prisma/prisma/packages/client/tests/e2e/nextjs-schema-not-found/9_monorepo-noServerComponents-customOutput-noReExport/packages/service:
 ENOENT  ENOENT: no such file or directory, open '/tmp/prisma-0.0.0.tgz'

This error happened while installing a direct dependency of /tmp/renovate/repos/github/prisma/prisma/packages/client/tests/e2e/nextjs-schema-not-found/9_monorepo-noServerComponents-customOutput-noReExport/packages/service



Progress: resolved 1, reused 0, downloaded 0, added 0

File name: packages/client/tests/e2e/nextjs-schema-not-found/8_monorepo-serverComponents-noCustomOutput-noReExport/pnpm-lock.yaml
/tmp/renovate/repos/github/prisma/prisma/packages/client/tests/e2e/nextjs-schema-not-found/8_monorepo-serverComponents-noCustomOutput-noReExport/packages/service:
 ENOENT  ENOENT: no such file or directory, open '/tmp/prisma-0.0.0.tgz'

This error happened while installing a direct dependency of /tmp/renovate/repos/github/prisma/prisma/packages/client/tests/e2e/nextjs-schema-not-found/8_monorepo-serverComponents-noCustomOutput-noReExport/packages/service




File name: packages/client/tests/e2e/nextjs-schema-not-found/7_monorepo-noServerComponents-noCustomOutput-noReExport/pnpm-lock.yaml
/tmp/renovate/repos/github/prisma/prisma/packages/client/tests/e2e/nextjs-schema-not-found/7_monorepo-noServerComponents-noCustomOutput-noReExport/packages/service:
 ENOENT  ENOENT: no such file or directory, open '/tmp/prisma-0.0.0.tgz'

This error happened while installing a direct dependency of /tmp/renovate/repos/github/prisma/prisma/packages/client/tests/e2e/nextjs-schema-not-found/7_monorepo-noServerComponents-noCustomOutput-noReExport/packages/service



Progress: resolved 1, reused 0, downloaded 0, added 0

File name: packages/client/tests/e2e/nextjs-schema-not-found/6_simplerepo-serverComponents-customOutput-noReExport/pnpm-lock.yaml
 ENOENT  ENOENT: no such file or directory, open '/tmp/prisma-0.0.0.tgz'

This error happened while installing a direct dependency of /tmp/renovate/repos/github/prisma/prisma/packages/client/tests/e2e/nextjs-schema-not-found/6_simplerepo-serverComponents-customOutput-noReExport



Progress: resolved 1, reused 0, downloaded 0, added 0

File name: packages/client/tests/e2e/nextjs-schema-not-found/5_simplerepo-noServerComponents-customOutput-noReExport/pnpm-lock.yaml
 ENOENT  ENOENT: no such file or directory, open '/tmp/prisma-0.0.0.tgz'

This error happened while installing a direct dependency of /tmp/renovate/repos/github/prisma/prisma/packages/client/tests/e2e/nextjs-schema-not-found/5_simplerepo-noServerComponents-customOutput-noReExport



Progress: resolved 1, reused 0, downloaded 0, added 0

File name: packages/client/tests/e2e/nextjs-schema-not-found/4_simplerepo-serverComponents-noCustomOutput-noReExport/pnpm-lock.yaml
 ENOENT  ENOENT: no such file or directory, open '/tmp/prisma-0.0.0.tgz'

This error happened while installing a direct dependency of /tmp/renovate/repos/github/prisma/prisma/packages/client/tests/e2e/nextjs-schema-not-found/4_simplerepo-serverComponents-noCustomOutput-noReExport




File name: packages/client/tests/e2e/nextjs-schema-not-found/3_simplerepo-noServerComponents-noCustomOutput-noReExport/pnpm-lock.yaml
 ENOENT  ENOENT: no such file or directory, open '/tmp/prisma-0.0.0.tgz'

This error happened while installing a direct dependency of /tmp/renovate/repos/github/prisma/prisma/packages/client/tests/e2e/nextjs-schema-not-found/3_simplerepo-noServerComponents-noCustomOutput-noReExport




File name: packages/client/tests/e2e/nextjs-schema-not-found/18_monorepo-serverComponents-customOutput-reExportIndirect-ts/pnpm-lock.yaml
Scope: all 2 workspace projects
/tmp/renovate/repos/github/prisma/prisma/packages/client/tests/e2e/nextjs-schema-not-found/18_monorepo-serverComponents-customOutput-reExportIndirect-ts/packages/db:
 ENOENT  ENOENT: no such file or directory, open '/tmp/prisma-0.0.0.tgz'

This error happened while installing a direct dependency of /tmp/renovate/repos/github/prisma/prisma/packages/client/tests/e2e/nextjs-schema-not-found/18_monorepo-serverComponents-customOutput-reExportIndirect-ts/packages/db




File name: packages/client/tests/e2e/nextjs-schema-not-found/17_monorepo-noServerComponents-customOutput-reExportIndirect-ts/pnpm-lock.yaml
Scope: all 3 workspace projects
/tmp/renovate/repos/github/prisma/prisma/packages/client/tests/e2e/nextjs-schema-not-found/17_monorepo-noServerComponents-customOutput-reExportIndirect-ts/packages/db:
 ENOENT  ENOENT: no such file or directory, open '/tmp/prisma-0.0.0.tgz'

This error happened while installing a direct dependency of /tmp/renovate/repos/github/prisma/prisma/packages/client/tests/e2e/nextjs-schema-not-found/17_monorepo-noServerComponents-customOutput-reExportIndirect-ts/packages/db




File name: packages/client/tests/e2e/nextjs-schema-not-found/16_monorepo-serverComponents-customOutput-reExportIndirect/pnpm-lock.yaml
Scope: all 2 workspace projects
/tmp/renovate/repos/github/prisma/prisma/packages/client/tests/e2e/nextjs-schema-not-found/16_monorepo-serverComponents-customOutput-reExportIndirect/packages/db:
 ENOENT  ENOENT: no such file or directory, open '/tmp/prisma-0.0.0.tgz'

This error happened while installing a direct dependency of /tmp/renovate/repos/github/prisma/prisma/packages/client/tests/e2e/nextjs-schema-not-found/16_monorepo-serverComponents-customOutput-reExportIndirect/packages/db




File name: packages/client/tests/e2e/nextjs-schema-not-found/15_monorepo-noServerComponents-customOutput-reExportIndirect/pnpm-lock.yaml
Scope: all 3 workspace projects
/tmp/renovate/repos/github/prisma/prisma/packages/client/tests/e2e/nextjs-schema-not-found/15_monorepo-noServerComponents-customOutput-reExportIndirect/packages/db:
 ENOENT  ENOENT: no such file or directory, open '/tmp/prisma-0.0.0.tgz'

This error happened while installing a direct dependency of /tmp/renovate/repos/github/prisma/prisma/packages/client/tests/e2e/nextjs-schema-not-found/15_monorepo-noServerComponents-customOutput-reExportIndirect/packages/db



Progress: resolved 1, reused 0, downloaded 0, added 0

File name: packages/client/tests/e2e/nextjs-schema-not-found/14_monorepo-serverComponents-customOutput-reExportDirect/pnpm-lock.yaml
Scope: all 2 workspace projects
/tmp/renovate/repos/github/prisma/prisma/packages/client/tests/e2e/nextjs-schema-not-found/14_monorepo-serverComponents-customOutput-reExportDirect/packages/service:
 ENOENT  ENOENT: no such file or directory, open '/tmp/prisma-nextjs-monorepo-workaround-plugin-0.0.0.tgz'

This error happened while installing a direct dependency of /tmp/renovate/repos/github/prisma/prisma/packages/client/tests/e2e/nextjs-schema-not-found/14_monorepo-serverComponents-customOutput-reExportDirect/packages/service




File name: packages/client/tests/e2e/nextjs-schema-not-found/13_monorepo-noServerComponents-customOutput-reExportDirect/pnpm-lock.yaml
Scope: all 2 workspace projects
/tmp/renovate/repos/github/prisma/prisma/packages/client/tests/e2e/nextjs-schema-not-found/13_monorepo-noServerComponents-customOutput-reExportDirect/packages/service:
 ENOENT  ENOENT: no such file or directory, open '/tmp/prisma-nextjs-monorepo-workaround-plugin-0.0.0.tgz'

This error happened while installing a direct dependency of /tmp/renovate/repos/github/prisma/prisma/packages/client/tests/e2e/nextjs-schema-not-found/13_monorepo-noServerComponents-customOutput-reExportDirect/packages/service



packages/service                         |  WARN  Installing a dependency from a non-existent directory: /tmp/renovate/repos/github/prisma/prisma/packages/client/tests/e2e/nextjs-schema-not-found/13_monorepo-noServerComponents-customOutput-reExportDirect/packages/db

File name: packages/client/tests/e2e/nextjs-schema-not-found/12_monorepo-serverComponents-noCustomOutput-reExportIndirect/pnpm-lock.yaml
Scope: all 2 workspace projects
/tmp/renovate/repos/github/prisma/prisma/packages/client/tests/e2e/nextjs-schema-not-found/12_monorepo-serverComponents-noCustomOutput-reExportIndirect/packages/db:
 ENOENT  ENOENT: no such file or directory, open '/tmp/prisma-0.0.0.tgz'

This error happened while installing a direct dependency of /tmp/renovate/repos/github/prisma/prisma/packages/client/tests/e2e/nextjs-schema-not-found/12_monorepo-serverComponents-noCustomOutput-reExportIndirect/packages/db



Progress: resolved 1, reused 0, downloaded 0, added 0

File name: packages/client/tests/e2e/nextjs-schema-not-found/11_monorepo-noServerComponents-noCustomOutput-reExportIndirect/pnpm-lock.yaml
Scope: all 3 workspace projects
/tmp/renovate/repos/github/prisma/prisma/packages/client/tests/e2e/nextjs-schema-not-found/11_monorepo-noServerComponents-noCustomOutput-reExportIndirect/packages/db:
 ENOENT  ENOENT: no such file or directory, open '/tmp/prisma-0.0.0.tgz'

This error happened while installing a direct dependency of /tmp/renovate/repos/github/prisma/prisma/packages/client/tests/e2e/nextjs-schema-not-found/11_monorepo-noServerComponents-noCustomOutput-reExportIndirect/packages/db




File name: packages/client/tests/e2e/nextjs-schema-not-found/10_monorepo-serverComponents-customOutput-noReExport/pnpm-lock.yaml
/tmp/renovate/repos/github/prisma/prisma/packages/client/tests/e2e/nextjs-schema-not-found/10_monorepo-serverComponents-customOutput-noReExport/packages/service:
 ENOENT  ENOENT: no such file or directory, open '/tmp/prisma-0.0.0.tgz'

This error happened while installing a direct dependency of /tmp/renovate/repos/github/prisma/prisma/packages/client/tests/e2e/nextjs-schema-not-found/10_monorepo-serverComponents-customOutput-noReExport/packages/service




File name: packages/client/tests/e2e/issues/19999-tsc-extensions-oom/pnpm-lock.yaml
undefined
 ENOENT  ENOENT: no such file or directory, open '/tmp/prisma-0.0.0.tgz'

This error happened while installing a direct dependency of /tmp/renovate/repos/github/prisma/prisma/packages/client/tests/e2e/issues/19999-tsc-extensions-oom




File name: packages/client/tests/e2e/issues/19866-ts-composite-declaration/pnpm-lock.yaml
undefined
 ENOENT  ENOENT: no such file or directory, open '/tmp/prisma-0.0.0.tgz'

This error happened while installing a direct dependency of /tmp/renovate/repos/github/prisma/prisma/packages/client/tests/e2e/issues/19866-ts-composite-declaration



Progress: resolved 1, reused 0, downloaded 0, added 0

File name: packages/client/tests/e2e/invalid-package-version/pnpm-lock.yaml
undefined
 ENOENT  ENOENT: no such file or directory, open '/tmp/prisma-0.0.0.tgz'

This error happened while installing a direct dependency of /tmp/renovate/repos/github/prisma/prisma/packages/client/tests/e2e/invalid-package-version




File name: packages/client/tests/e2e/example/pnpm-lock.yaml
undefined
 ENOENT  ENOENT: no such file or directory, open '/tmp/prisma-0.0.0.tgz'

This error happened while installing a direct dependency of /tmp/renovate/repos/github/prisma/prisma/packages/client/tests/e2e/example




File name: packages/client/tests/e2e/enum-import-in-edge/pnpm-lock.yaml
undefined
 ENOENT  ENOENT: no such file or directory, open '/tmp/prisma-0.0.0.tgz'

This error happened while installing a direct dependency of /tmp/renovate/repos/github/prisma/prisma/packages/client/tests/e2e/enum-import-in-edge




File name: packages/client/tests/e2e/engine-not-found-error/tooling-tampered-with-engine-copy/pnpm-lock.yaml
undefined
 ENOENT  ENOENT: no such file or directory, open '/tmp/prisma-0.0.0.tgz'

This error happened while installing a direct dependency of /tmp/renovate/repos/github/prisma/prisma/packages/client/tests/e2e/engine-not-found-error/tooling-tampered-with-engine-copy



Progress: resolved 1, reused 0, downloaded 0, added 0

File name: packages/client/tests/e2e/engine-not-found-error/native-generated-different-platform/pnpm-lock.yaml
undefined
 ENOENT  ENOENT: no such file or directory, open '/tmp/prisma-0.0.0.tgz'

This error happened while installing a direct dependency of /tmp/renovate/repos/github/prisma/prisma/packages/client/tests/e2e/engine-not-found-error/native-generated-different-platform



Progress: resolved 1, reused 0, downloaded 0, added 0

File name: packages/client/tests/e2e/engine-not-found-error/bundler-tampered-with-engine-copy/pnpm-lock.yaml
undefined
 ENOENT  ENOENT: no such file or directory, open '/tmp/prisma-0.0.0.tgz'

This error happened while installing a direct dependency of /tmp/renovate/repos/github/prisma/prisma/packages/client/tests/e2e/engine-not-found-error/bundler-tampered-with-engine-copy



Progress: resolved 1, reused 0, downloaded 0, added 0

File name: packages/client/tests/e2e/engine-not-found-error/binary-targets-incorrectly-pinned/pnpm-lock.yaml
undefined
 ENOENT  ENOENT: no such file or directory, open '/tmp/prisma-0.0.0.tgz'

This error happened while installing a direct dependency of /tmp/renovate/repos/github/prisma/prisma/packages/client/tests/e2e/engine-not-found-error/binary-targets-incorrectly-pinned




File name: packages/client/tests/e2e/driver-adapters-accelerate/pnpm-lock.yaml
undefined
 ENOENT  ENOENT: no such file or directory, open '/tmp/prisma-0.0.0.tgz'

This error happened while installing a direct dependency of /tmp/renovate/repos/github/prisma/prisma/packages/client/tests/e2e/driver-adapters-accelerate



Progress: resolved 1, reused 0, downloaded 0, added 0

File name: packages/client/tests/e2e/default-version/pnpm-lock.yaml
undefined
 ENOENT  ENOENT: no such file or directory, open '/tmp/prisma-client-0.0.0.tgz'

This error happened while installing a direct dependency of /tmp/renovate/repos/github/prisma/prisma/packages/client/tests/e2e/default-version




File name: packages/client/tests/e2e/connection-limit-reached/pnpm-lock.yaml
undefined
 ENOENT  ENOENT: no such file or directory, open '/tmp/prisma-0.0.0.tgz'

This error happened while installing a direct dependency of /tmp/renovate/repos/github/prisma/prisma/packages/client/tests/e2e/connection-limit-reached




File name: packages/client/tests/e2e/bundler-detection-error/pnpm-lock.yaml
undefined
 ENOENT  ENOENT: no such file or directory, open '/tmp/prisma-0.0.0.tgz'

This error happened while installing a direct dependency of /tmp/renovate/repos/github/prisma/prisma/packages/client/tests/e2e/bundler-detection-error



Progress: resolved 1, reused 0, downloaded 0, added 0

File name: packages/client/tests/e2e/browser-unsupported-errors/pnpm-lock.yaml
undefined
 ENOENT  ENOENT: no such file or directory, open '/tmp/prisma-0.0.0.tgz'

This error happened while installing a direct dependency of /tmp/renovate/repos/github/prisma/prisma/packages/client/tests/e2e/browser-unsupported-errors



Progress: resolved 1, reused 0, downloaded 0, added 0

File name: packages/client/tests/e2e/adapter-d1-itx-error/pnpm-lock.yaml
undefined
 ENOENT  ENOENT: no such file or directory, open '/tmp/prisma-0.0.0.tgz'

This error happened while installing a direct dependency of /tmp/renovate/repos/github/prisma/prisma/packages/client/tests/e2e/adapter-d1-itx-error




File name: packages/client/tests/e2e/accelerate-types/pnpm-lock.yaml
undefined
 ENOENT  ENOENT: no such file or directory, open '/tmp/prisma-0.0.0.tgz'

This error happened while installing a direct dependency of /tmp/renovate/repos/github/prisma/prisma/packages/client/tests/e2e/accelerate-types




Copy link
Contributor

github-actions bot commented Feb 15, 2024

size-limit report 📦

Path Size
packages/client/runtime/library.js 179.64 KB (0%)
packages/client/runtime/library.d.ts 81 B (0%)
packages/client/runtime/binary.js 600.86 KB (0%)
packages/client/runtime/binary.d.ts 26 B (0%)
packages/client/runtime/edge.js 158.91 KB (0%)
packages/client/runtime/edge-esm.js 158.8 KB (0%)
packages/client/runtime/wasm.js 114.75 KB (0%)
packages/client/runtime/index-browser.js 33.77 KB (0%)
packages/client/runtime/index-browser.d.ts 89 B (0%)
packages/cli/build/index.js 2.09 MB (0%)
packages/client/prisma-client-0.0.0.tgz 3.01 MB (0%)
packages/cli/prisma-0.0.0.tgz 3.74 MB (0%)
packages/bundle-size/da-workers-libsql/output.tgz 882.47 KB (0%)
packages/bundle-size/da-workers-neon/output.tgz 961.67 KB (0%)
packages/bundle-size/da-workers-pg/output.tgz 980.4 KB (0%)
packages/bundle-size/da-workers-pg-worker/output.tgz 936.12 KB (0%)
packages/bundle-size/da-workers-planetscale/output.tgz 898.64 KB (0%)
packages/bundle-size/da-workers-d1/output.tgz 855.55 KB (0%)

Copy link

socket-security bot commented Feb 16, 2024

Copy link
Member

@Jolg42 Jolg42 left a comment

Choose a reason for hiding this comment

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

Let's stay on v18 for now?

Copy link

socket-security bot commented Feb 21, 2024

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert Package NoteSource
Install scripts npm/workerd@1.20230814.1

View full report↗︎

Next steps

What is an install script?

Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts.

Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

  • @SocketSecurity ignore npm/workerd@1.20230814.1

@renovate renovate bot force-pushed the renovate/major-e2e-tests branch from 2418189 to 7c96797 Compare March 6, 2024 01:39
@renovate renovate bot changed the title chore(deps): update e2e tests (major) fix(deps): update e2e tests (major) Mar 6, 2024
Copy link

codspeed-hq bot commented Mar 6, 2024

CodSpeed Performance Report

Merging #23143 will degrade performances by 24.38%

Comparing renovate/major-e2e-tests (38e1f66) with main (037c380)

Summary

❌ 1 regressions
✅ 2 untouched benchmarks

⚠️ Please fix the performance issues or acknowledge them on CodSpeed.

Benchmarks breakdown

Benchmark main renovate/major-e2e-tests Change
client generation 100 models with relations 28.9 s 38.2 s -24.38%

@renovate renovate bot force-pushed the renovate/major-e2e-tests branch from 7c96797 to 3f3384a Compare March 13, 2024 01:51
@renovate renovate bot force-pushed the renovate/major-e2e-tests branch from 3f3384a to b98e299 Compare March 20, 2024 06:36
@renovate renovate bot force-pushed the renovate/major-e2e-tests branch 2 times, most recently from 66ec0f7 to 19c7517 Compare April 3, 2024 06:57
@renovate renovate bot force-pushed the renovate/major-e2e-tests branch 2 times, most recently from 8e65106 to f3ea3d0 Compare April 17, 2024 00:56
Copy link
Contributor

github-actions bot commented Apr 17, 2024

Client memory tests, node 18, library:

✅ Success

@renovate renovate bot force-pushed the renovate/major-e2e-tests branch from f3ea3d0 to 85d6668 Compare April 24, 2024 06:38
@renovate renovate bot force-pushed the renovate/major-e2e-tests branch from 85d6668 to 38e1f66 Compare May 1, 2024 02:13
@renovate renovate bot changed the title fix(deps): update e2e tests (major) chore(deps): update e2e tests (major) May 1, 2024
@Jolg42 Jolg42 closed this May 3, 2024
@Jolg42 Jolg42 deleted the renovate/major-e2e-tests branch May 3, 2024 15:53
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.

None yet

1 participant