chore(deps): update e2e tests #24108

renovate · 2024-05-08T02:10:40Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@types/node (source)	`16.18.96` -> `16.18.97`
@types/node (source)	`16.18.96` -> `16.18.97`
@types/node (source)	`16.18.96` -> `16.18.97`
@types/node (source)	`16.18.96` -> `16.18.97`
@types/node (source)	`16.18.96` -> `16.18.97`
@types/node (source)	`18.19.31` -> `18.19.33`
@types/react (source)	`18.3.1` -> `18.3.2`
esbuild	`0.20.2` -> `0.21.3`
esbuild	`0.20.2` -> `0.21.3`
wrangler (source)	`3.53.0` -> `3.57.1`
wrangler (source)	`3.53.0` -> `3.57.1`
wrangler (source)	`3.53.0` -> `3.57.1`

Release Notes

evanw/esbuild (esbuild)

`v0.21.3`

Compare Source

Implement the decorator metadata proposal (#3760)

This release implements the decorator metadata proposal, which is a sub-proposal of the decorators proposal. Microsoft shipped the decorators proposal in TypeScript 5.0 and the decorator metadata proposal in TypeScript 5.2, so it's important that esbuild also supports both of these features. Here's a quick example:
```
// Shim the "Symbol.metadata" symbol
Symbol.metadata ??= Symbol('Symbol.metadata')

const track = (_, context) => {
  (context.metadata.names ||= []).push(context.name)
}

class Foo {
  @&#8203;track foo = 1
  @&#8203;track bar = 2
}

// Prints ["foo", "bar"]
console.log(Foo[Symbol.metadata].names)
```
⚠️ WARNING ⚠️

This proposal has been marked as "stage 3" which means "recommended for implementation". However, it's still a work in progress and isn't a part of JavaScript yet, so keep in mind that any code that uses JavaScript decorator metadata may need to be updated as the feature continues to evolve. If/when that happens, I will update esbuild's implementation to match the specification. I will not be supporting old versions of the specification.
Fix bundled decorators in derived classes (#3768)

In certain cases, bundling code that uses decorators in a derived class with a class body that references its own class name could previously generate code that crashes at run-time due to an incorrect variable name. This problem has been fixed. Here is an example of code that was compiled incorrectly before this fix:
```
class Foo extends Object {
  @&#8203;(x => x) foo() {
    return Foo
  }
}
console.log(new Foo().foo())
```
Fix tsconfig.json files inside symlinked directories (#3767)

This release fixes an issue with a scenario involving a tsconfig.json file that extends another file from within a symlinked directory that uses the paths feature. In that case, the implicit baseURL value should be based on the real path (i.e. after expanding all symbolic links) instead of the original path. This was already done for other files that esbuild resolves but was not yet done for tsconfig.json because it's special-cased (the regular path resolver can't be used because the information inside tsconfig.json is involved in path resolution). Note that this fix no longer applies if the --preserve-symlinks setting is enabled.

`v0.21.2`

Compare Source

Correct this in field and accessor decorators (#3761)

This release changes the value of this in initializers for class field and accessor decorators from the module-level this value to the appropriate this value for the decorated element (either the class or the instance). It was previously incorrect due to lack of test coverage. Here's an example of a decorator that doesn't work without this change:
```
const dec = () => function() { this.bar = true }
class Foo { @&#8203;dec static foo }
console.log(Foo.bar) // Should be "true"
```
Allow es2023 as a target environment (#3762)

TypeScript recently added es2023 as a compilation target, so esbuild now supports this too. There is no difference between a target of es2022 and es2023 as far as esbuild is concerned since the 2023 edition of JavaScript doesn't introduce any new syntax features.

`v0.21.1`

Compare Source

Fix a regression with --keep-names (#3756)

The previous release introduced a regression with the --keep-names setting and object literals with get/set accessor methods, in which case the generated code contained syntax errors. This release fixes the regression:
```
// Original code
x = { get y() {} }

// Output from version 0.21.0 (with --keep-names)
x = { get y: /* @&#8203;__PURE__ */ __name(function() {
}, "y") };

// Output from this version (with --keep-names)
x = { get y() {
} };
```

`v0.21.0`

Compare Source

This release doesn't contain any deliberately-breaking changes. However, it contains a very complex new feature and while all of esbuild's tests pass, I would not be surprised if an important edge case turns out to be broken. So I'm releasing this as a breaking change release to avoid causing any trouble. As usual, make sure to test your code when you upgrade.

Implement the JavaScript decorators proposal (#104)

With this release, esbuild now contains an implementation of the upcoming JavaScript decorators proposal. This is the same feature that shipped in TypeScript 5.0 and has been highly-requested on esbuild's issue tracker. You can read more about them in that blog post and in this other (now slightly outdated) extensive blog post here: https://2ality.com/2022/10/javascript-decorators.html. Here's a quick example:
```
const log = (fn, context) => function() {
  console.log(`before ${context.name}`)
  const it = fn.apply(this, arguments)
  console.log(`after ${context.name}`)
  return it
}

class Foo {
  @&#8203;log static foo() {
    console.log('in foo')
  }
}

// Logs "before foo", "in foo", "after foo"
Foo.foo()
```
Note that this feature is different than the existing "TypeScript experimental decorators" feature that esbuild already implements. It uses similar syntax but behaves very differently, and the two are not compatible (although it's sometimes possible to write decorators that work with both). TypeScript experimental decorators will still be supported by esbuild going forward as they have been around for a long time, are very widely used, and let you do certain things that are not possible with JavaScript decorators (such as decorating function parameters). By default esbuild will parse and transform JavaScript decorators, but you can tell esbuild to parse and transform TypeScript experimental decorators instead by setting "experimentalDecorators": true in your tsconfig.json file.

Probably at least half of the work for this feature went into creating a test suite that exercises many of the proposal's edge cases: https://github.com/evanw/decorator-tests. It has given me a reasonable level of confidence that esbuild's initial implementation is acceptable. However, I don't have access to a significant sample of real code that uses JavaScript decorators. If you're currently using JavaScript decorators in a real code base, please try out esbuild's implementation and let me know if anything seems off.

⚠️ WARNING ⚠️

This proposal has been in the works for a very long time (work began around 10 years ago in 2014) and it is finally getting close to becoming part of the JavaScript language. However, it's still a work in progress and isn't a part of JavaScript yet, so keep in mind that any code that uses JavaScript decorators may need to be updated as the feature continues to evolve. The decorators proposal is pretty close to its final form but it can and likely will undergo some small behavioral adjustments before it ends up becoming a part of the standard. If/when that happens, I will update esbuild's implementation to match the specification. I will not be supporting old versions of the specification.

Optimize the generated code for private methods

Previously when lowering private methods for old browsers, esbuild would generate one WeakSet for each private method. This mirrors similar logic for generating one WeakSet for each private field. Using a separate WeakMap for private fields is necessary as their assignment can be observable:

let it
class Bar {
  constructor() {
    it = this
  }
}
class Foo extends Bar {
  #x = 1
  #y = null.foo
  static check() {
    console.log(#x in it, #y in it)
  }
}
try { new Foo } catch {}
Foo.check()

This prints true false because this partially-initialized instance has #x but not #y. In other words, it's not true that all class instances will always have all of their private fields. However, the assignment of private methods to a class instance is not observable. In other words, it's true that all class instances will always have all of their private methods. This means esbuild can lower private methods into code where all methods share a single WeakSet, which is smaller, faster, and uses less memory. Other JavaScript processing tools such as the TypeScript compiler already make this optimization. Here's what this change looks like:

// Original code
class Foo {
  #x() { return this.#x() }
  #y() { return this.#y() }
  #z() { return this.#z() }
}

// Old output (--supported:class-private-method=false)
var _x, x_fn, _y, y_fn, _z, z_fn;
class Foo {
  constructor() {
    __privateAdd(this, _x);
    __privateAdd(this, _y);
    __privateAdd(this, _z);
  }
}
_x = new WeakSet();
x_fn = function() {
  return __privateMethod(this, _x, x_fn).call(this);
};
_y = new WeakSet();
y_fn = function() {
  return __privateMethod(this, _y, y_fn).call(this);
};
_z = new WeakSet();
z_fn = function() {
  return __privateMethod(this, _z, z_fn).call(this);
};

// New output (--supported:class-private-method=false)
var _Foo_instances, x_fn, y_fn, z_fn;
class Foo {
  constructor() {
    __privateAdd(this, _Foo_instances);
  }
}
_Foo_instances = new WeakSet();
x_fn = function() {
  return __privateMethod(this, _Foo_instances, x_fn).call(this);
};
y_fn = function() {
  return __privateMethod(this, _Foo_instances, y_fn).call(this);
};
z_fn = function() {
  return __privateMethod(this, _Foo_instances, z_fn).call(this);
};

Fix an obscure bug with lowering class members with computed property keys

When class members that use newer syntax features are transformed for older target environments, they sometimes need to be relocated. However, care must be taken to not reorder any side effects caused by computed property keys. For example, the following code must evaluate a() then b() then c():
```
class Foo {
  [a()]() {}
  [b()];
  static { c() }
}
```
Previously esbuild did this by shifting the computed property key forward to the next spot in the evaluation order. Classes evaluate all computed keys first and then all static class elements, so if the last computed key needs to be shifted, esbuild previously inserted a static block at start of the class body, ensuring it came before all other static class elements:
```
var _a;
class Foo {
  constructor() {
    __publicField(this, _a);
  }
  static {
    _a = b();
  }
  [a()]() {
  }
  static {
    c();
  }
}
```
However, this could cause esbuild to accidentally generate a syntax error if the computed property key contains code that isn't allowed in a static block, such as an await expression. With this release, esbuild fixes this problem by shifting the computed property key backward to the previous spot in the evaluation order instead, which may push it into the extends clause or even before the class itself:
```
// Original code
class Foo {
  [a()]() {}
  [await b()];
  static { c() }
}

// Old output (with --supported:class-field=false)
var _a;
class Foo {
  constructor() {
    __publicField(this, _a);
  }
  static {
    _a = await b();
  }
  [a()]() {
  }
  static {
    c();
  }
}

// New output (with --supported:class-field=false)
var _a, _b;
class Foo {
  constructor() {
    __publicField(this, _a);
  }
  [(_b = a(), _a = await b(), _b)]() {
  }
  static {
    c();
  }
}
```
Fix some --keep-names edge cases

The NamedEvaluation syntax-directed operation in the JavaScript specification gives certain anonymous expressions a name property depending on where they are in the syntax tree. For example, the following initializers convey a name value:
```
var foo = function() {}
var bar = class {}
console.log(foo.name, bar.name)
```
When you enable esbuild's --keep-names setting, esbuild generates additional code to represent this NamedEvaluation operation so that the value of the name property persists even when the identifiers are renamed (e.g. due to minification).

However, I recently learned that esbuild's implementation of NamedEvaluation is missing a few cases. Specifically esbuild was missing property definitions, class initializers, logical-assignment operators. These cases should now all be handled:
```
var obj = { foo: function() {} }
class Foo0 { foo = function() {} }
class Foo1 { static foo = function() {} }
class Foo2 { accessor foo = function() {} }
class Foo3 { static accessor foo = function() {} }
foo ||= function() {}
foo &&= function() {}
foo ??= function() {}
```

`v0.20.2`

Compare Source

Support TypeScript experimental decorators on abstract class fields (#3684)

With this release, you can now use TypeScript experimental decorators on abstract class fields. This was silently compiled incorrectly in esbuild 0.19.7 and below, and was an error from esbuild 0.19.8 to esbuild 0.20.1. Code such as the following should now work correctly:

// Original code
const log = (x: any, y: string) => console.log(y)
abstract class Foo { @&#8203;log abstract foo: string }
new class extends Foo { foo = '' }

// Old output (with --loader=ts --tsconfig-raw={\"compilerOptions\":{\"experimentalDecorators\":true}})
const log = (x, y) => console.log(y);
class Foo {
}
new class extends Foo {
  foo = "";
}();

// New output (with --loader=ts --tsconfig-raw={\"compilerOptions\":{\"experimentalDecorators\":true}})
const log = (x, y) => console.log(y);
class Foo {
}
__decorateClass([
  log
], Foo.prototype, "foo", 2);
new class extends Foo {
  foo = "";
}();

JSON loader now preserves __proto__ properties (#3700)

Copying JSON source code into a JavaScript file will change its meaning if a JSON object contains the __proto__ key. A literal __proto__ property in a JavaScript object literal sets the prototype of the object instead of adding a property named __proto__, while a literal __proto__ property in a JSON object literal just adds a property named __proto__. With this release, esbuild will now work around this problem by converting JSON to JavaScript with a computed property key in this case:

// Original code
import data from 'data:application/json,{"__proto__":{"fail":true}}'
if (Object.getPrototypeOf(data)?.fail) throw 'fail'

// Old output (with --bundle)
(() => {
  // <data:application/json,{"__proto__":{"fail":true}}>
  var json_proto_fail_true_default = { __proto__: { fail: true } };

  // entry.js
  if (Object.getPrototypeOf(json_proto_fail_true_default)?.fail)
    throw "fail";
})();

// New output (with --bundle)
(() => {
  // <data:application/json,{"__proto__":{"fail":true}}>
  var json_proto_fail_true_default = { ["__proto__"]: { fail: true } };

  // example.mjs
  if (Object.getPrototypeOf(json_proto_fail_true_default)?.fail)
    throw "fail";
})();

Improve dead code removal of switch statements (#3659)

With this release, esbuild will now remove switch statements in branches when minifying if they are known to never be evaluated:

// Original code
if (true) foo(); else switch (bar) { case 1: baz(); break }

// Old output (with --minify)
if(1)foo();else switch(bar){case 1:}

// New output (with --minify)
foo();

Empty enums should behave like an object literal (#3657)

TypeScript allows you to create an empty enum and add properties to it at run time. While people usually use an empty object literal for this instead of a TypeScript enum, esbuild's enum transform didn't anticipate this use case and generated undefined instead of {} for an empty enum. With this release, you can now use an empty enum to generate an empty object literal.
```
// Original code
enum Foo {}

// Old output (with --loader=ts)
var Foo = /* @&#8203;__PURE__ */ ((Foo2) => {
})(Foo || {});

// New output (with --loader=ts)
var Foo = /* @&#8203;__PURE__ */ ((Foo2) => {
  return Foo2;
})(Foo || {});
```
Handle Yarn Plug'n'Play edge case with tsconfig.json (#3698)

Previously a tsconfig.json file that extends another file in a package with an exports map failed to work when Yarn's Plug'n'Play resolution was active. This edge case should work now starting with this release.
Work around issues with Deno 1.31+ (#3682)

Version 0.20.0 of esbuild changed how the esbuild child process is run in esbuild's API for Deno. Previously it used Deno.run but that API is being removed in favor of Deno.Command. As part of this change, esbuild is now calling the new unref function on esbuild's long-lived child process, which is supposed to allow Deno to exit when your code has finished running even though the child process is still around (previously you had to explicitly call esbuild's stop() function to terminate the child process for Deno to be able to exit).

However, this introduced a problem for Deno's testing API which now fails some tests that use esbuild with error: Promise resolution is still pending but the event loop has already resolved. It's unclear to me why this is happening. The call to unref was recommended by someone on the Deno core team, and calling Node's equivalent unref API has been working fine for esbuild in Node for a long time. It could be that I'm using it incorrectly, or that there's some reference counting and/or garbage collection bug in Deno's internals, or that Deno's unref just works differently than Node's unref. In any case, it's not good for Deno tests that use esbuild to be failing.

In this release, I am removing the call to unref to fix this issue. This means that you will now have to call esbuild's stop() function to allow Deno to exit, just like you did before esbuild version 0.20.0 when this regression was introduced.

Note: This regression wasn't caught earlier because Deno doesn't seem to fail tests that have outstanding setTimeout calls, which esbuild's test harness was using to enforce a maximum test runtime. Adding a setTimeout was allowing esbuild's Deno tests to succeed. So this regression doesn't necessarily apply to all people using tests in Deno.

`v0.20.1`

Compare Source

Fix a bug with the CSS nesting transform (#3648)

This release fixes a bug with the CSS nesting transform for older browsers where the generated CSS could be incorrect if a selector list contained a pseudo element followed by another selector. The bug was caused by incorrectly mutating the parent rule's selector list when filtering out pseudo elements for the child rules:
```
/* Original code */
.foo {
  &:after,
  & .bar {
    color: red;
  }
}

/* Old output (with --supported:nesting=false) */
.foo .bar,
.foo .bar {
  color: red;
}

/* New output (with --supported:nesting=false) */
.foo:after,
.foo .bar {
  color: red;
}
```
Constant folding for JavaScript inequality operators (#3645)

This release introduces constant folding for the < > <= >= operators. The minifier will now replace these operators with true or false when both sides are compile-time numeric or string constants:
```
// Original code
console.log(1 < 2, '🍕' > '🧀')

// Old output (with --minify)
console.log(1<2,"🍕">"🧀");

// New output (with --minify)
console.log(!0,!1);
```

Better handling of __proto__ edge cases (#3651)

JavaScript object literal syntax contains a special case where a non-computed property with a key of __proto__ sets the prototype of the object. This does not apply to computed properties or to properties that use the shorthand property syntax introduced in ES6. Previously esbuild didn't correctly preserve the "sets the prototype" status of properties inside an object literal, meaning a property that sets the prototype could accidentally be transformed into one that doesn't and vice versa. This has now been fixed:

// Original code
function foo(__proto__) {
  return { __proto__: __proto__ } // Note: sets the prototype
}
function bar(__proto__, proto) {
  {
    let __proto__ = proto
    return { __proto__ } // Note: doesn't set the prototype
  }
}

// Old output
function foo(__proto__) {
  return { __proto__ }; // Note: no longer sets the prototype (WRONG)
}
function bar(__proto__, proto) {
  {
    let __proto__2 = proto;
    return { __proto__: __proto__2 }; // Note: now sets the prototype (WRONG)
  }
}

// New output
function foo(__proto__) {
  return { __proto__: __proto__ }; // Note: sets the prototype (correct)
}
function bar(__proto__, proto) {
  {
    let __proto__2 = proto;
    return { ["__proto__"]: __proto__2 }; // Note: doesn't set the prototype (correct)
  }
}

Fix cross-platform non-determinism with CSS color space transformations (#3650)

The Go compiler takes advantage of "fused multiply and add" (FMA) instructions on certain processors which do the operation x*y + z without intermediate rounding. This causes esbuild's CSS color space math to differ on different processors (currently ppc64le and s390x), which breaks esbuild's guarantee of deterministic output. To avoid this, esbuild's color space math now inserts a float64() cast around every single math operation. This tells the Go compiler not to use the FMA optimization.
Fix a crash when resolving a path from a directory that doesn't exist (#3634)

This release fixes a regression where esbuild could crash when resolving an absolute path if the source directory for the path resolution operation doesn't exist. While this situation doesn't normally come up, it could come up when running esbuild concurrently with another operation that mutates the file system as esbuild is doing a build (such as using git to switch branches). The underlying problem was a regression that was introduced in version 0.18.0.

cloudflare/workers-sdk (wrangler)

`v3.57.1`

Compare Source

Patch Changes

#5859 f2ceb3a Thanks @w-kuhn! - fix: queue consumer max_batch_timeout should accept a 0 value
#5862 441a05f Thanks @CarmenPopoviciu! - fix: wrangler pages deploy should fail if deployment was unsuccessful

If a Pages project fails to deploy, wrangler pages deploy will log
an error message, but exit successfully. It should instead throw a
FatalError.
#5812 d5e00e4 Thanks @thomasgauvin! - fix: remove Hyperdrive warning for local development.

Hyperdrive bindings are now supported when developing locally with Hyperdrive. We should update our logs to reflect this.
#5626 a12b031 Thanks @RamIdeas! - chore: ignore workerd output (error: CODE_MOVED) not intended for end-user devs

`v3.57.0`

Compare Source

Minor Changes

#5696 7e97ba8 Thanks @geelen! - feature: Improved d1 execute --file --remote performance & added support for much larger SQL files within a single transaction.
#5819 63f7acb Thanks @CarmenPopoviciu! - fix: Show feedback on Pages project deployment failure

Today, if uploading a Pages Function, or deploying a Pages project fails for whatever reason, there’s no feedback shown to the user. Worse yet, the shown message is misleading, saying the deployment was successful, when in fact it was not:
```
✨ Deployment complete!
```
This commit ensures that we provide users with:
- the correct feedback with respect to their Pages deployment
- the appropriate messaging depending on the status of their project's deployment status
- the appropriate logs in case of a deployment failure
#5814 2869e03 Thanks @CarmenPopoviciu! - fix: Display correct global flags in wrangler pages --help

Running wrangler pages --help will list, amongst others, the following global flags:
```
-j, --experimental-json-config
-c, --config
-e, --env
-h, --help
-v, --version
```
This is not accurate, since flags such as --config, --experimental-json-config, or env are not supported by Pages.

This commit ensures we display the correct global flags that apply to Pages.
#5818 df2daf2 Thanks @WalshyDev! - chore: Deprecate usage of the deployment object on the unsafe metadata binding in favor of the new version_metadata binding.

If you're currently using the old binding, please move over to the new version_metadata binding by adding:
```
[version_metadata]
binding = "CF_VERSION_METADATA"
```
and updating your usage accordingly. You can find the docs for the new binding here: https://developers.cloudflare.com/workers/runtime-apis/bindings/version-metadata

Patch Changes

#5838 609debd Thanks @petebacondarwin! - fix: update undici to the latest version to avoid a potential vulnerability
#5832 86a6e09 Thanks @petebacondarwin! - fix: do not allow non-string values in bulk secret uploads

Prior to Wrangler 3.4.0 we displayed an error if the user tried to upload a
JSON file that contained non-string secrets, since these are not supported
by the Cloudflare backend.

This change reintroduces that check to give the user a helpful error message
rather than a cryptic workers.api.error.invalid_script_config error code.

`v3.56.0`

Compare Source

Minor Changes

#5712 151bc3d Thanks @penalosa! - feat: Support mtls_certificates and browser bindings when using wrangler.toml with a Pages project

Patch Changes

#5813 9627cef Thanks @GregBrimble! - fix: Upload Pages project assets with more grace
- Reduces the maximum bucket size from 50 MiB to 40 MiB.
- Reduces the maximum asset count from 5000 to 2000.
- Allows for more retries (with increased sleep between attempts) when encountering an API gateway failure.
Updated dependencies [0725f6f, 89b6d7f]:
- miniflare@3.20240512.0

`v3.55.0`

Compare Source

Minor Changes

#5570 66bdad0 Thanks @sesteves! - feature: support delayed delivery in the miniflare's queue simulator.

This change updates the miniflare's queue broker to support delayed delivery of messages, both when sending the message from a producer and when retrying the message from a consumer.

Patch Changes

#5740 97741db Thanks @WalshyDev! - chore: log "Version ID" in wrangler deploy, wrangler deployments list, wrangler deployments view and wrangler rollback to support migration from the deprecated "Deployment ID". Users should update any parsing to use "Version ID" before "Deployment ID" is removed.
#5754 f673c66 Thanks @RamIdeas! - fix: when using custom builds, the wrangler dev proxy server was sometimes left in a paused state

This could be observed as the browser loading indefinitely, after saving a source file (unchanged) when using custom builds. This is now fixed by ensuring the proxy server is unpaused after a short timeout period.
Updated dependencies [66bdad0, 9b4af8a]:
- miniflare@3.20240419.1

`v3.53.1`

Compare Source

Patch Changes

#5091 6365c90 Thanks @Cherry! - fix: better handle dashes and other invalid JS identifier characters in wrangler types generation for vars, bindings, etc.

Previously, with the following in your wrangler.toml, an invalid types file would be generated:
```
[vars]
some-var = "foobar"
```
Now, the generated types file will be valid:
```
interface Env {
	"some-var": "foobar";
}
```
#5748 27966a4 Thanks @penalosa! - fix: Load sourcemaps relative to the entry directory, not cwd.
#5746 1dd9f7e Thanks @petebacondarwin! - fix: suggest trying to update Wrangler if there is a newer one available after an unexpected error
#5226 f63e7a5 Thanks @DaniFoldi! - fix: remove second Wrangler banner from wrangler dispatch-namespace rename

`v3.53.0`

Compare Source

Minor Changes

#5604 327a456 Thanks @dario-piotrowicz! - feat: add support for environments in getPlatformProxy

allow getPlatformProxy to target environments by allowing users to specify an environment option

Example usage:
```
const { env } = await getPlatformProxy({
	environment: "production",
});
```

Patch Changes

#5705 4097759 Thanks @G4brym! - Add staging flag to AI binding

`v3.52.0`

Compare Source

Minor Changes

#5666 81d9615 Thanks @CarmenPopoviciu! - fix: Fix Pages config validation around Durable Objects

Today Pages cannot deploy Durable Objects itself. For this reason it is mandatory that when declaring Durable Objects bindings in the config file, the script_name is specified. We are currently not failing validation if
script_name is not specified but we should. These changes fix that.

Patch Changes

#5610 24840f6 Thanks @SuperchupuDev! - Mark ts-json-schema-generator as a dev dependency
#5669 a7e36d5 Thanks @dario-piotrowicz! - fix: fix broken Durable Object local proxying (when no cf property is present)

A regression was introduced in wrangler 3.46.0 (https://github.com/cloudflare/workers-sdk/pull/5215)
which made it so that missing Request#cf properties are serialized as "undefined", this in turn
throws a syntax parse error when such values are parsed via JSON.parse breaking the communication
with Durable Object local proxies. Fix such issue by serializing missing Request#cf properties as
"{}" instead.
#5616 c6312b5 Thanks @webbertakken! - fix: broken link to durable object migrations docs
#5482 1b7739e Thanks @DaniFoldi! - docs: show new Discord url everywhere for consistency. The old URL still works, but https://discord.cloudflare.com is preferred.
Updated dependencies [3a0d735, 1b7739e]:
- miniflare@3.20240419.0
- @cloudflare/kv-asset-handler @0.3.2

`v3.51.2`

Compare Source

Patch Changes

#5652 ccb9d3d Thanks @petebacondarwin! - chore: re-release due to broken build

`v3.51.0`

Compare Source

Minor Changes

#5477 9a46e03 Thanks @pmiguel! - feature: Changed Queues client to use the new QueueId and ConsumerId-based endpoints.
#5172 fbe1c9c Thanks @GregBrimble! - feat: Allow marking external modules (with --external) to avoid bundling them when building Pages Functions

It's useful for Pages Plugins which want to declare a peer dependency.

Patch Changes

#5585 22f5841 Thanks @geelen! - Updates wrangler d1 export to handle larger DBs more efficiently
Updated dependencies [c9f081a, c9f081a]:
- miniflare@3.20240405.2

`v3.50.0`

Compare Source

Minor Changes

#5587 d95450f Thanks @CarmenPopoviciu! - fix: pages functions build-env should throw error if invalid Pages config file is found
#5572 65aa21c Thanks @CarmenPopoviciu! - fix: fix pages function build-env to exit with code rather than throw fatal error

Currently pages functions build-env throws a fatal error if a config file does not exit, or if it is invalid. This causes issues for the CI system. We should instead exit with a specific code, if any of those situations arises.
#5291 ce00a44 Thanks @pmiguel! - feature: Added bespoke OAuth scope for Queues management.

Patch Changes

Updated dependencies [08b4908]:
- miniflare@3.20240405.1

`v3.49.0`

Compare Source

Minor Changes

#5549 113ac41 Thanks @penalosa! - feat: Support wrangler pages secret put|delete|list|bulk
#5550 4f47f74 Thanks @penalosa! - feat: Generate a JSON schema for the Wrangler package & use it in templates
#5561 59591cd Thanks @ocsfrank! - feat: update R2 CreateBucket action to include the storage class in the request body

Patch Changes

#5374 7999dd2 Thanks @maxwellpeterson! - fix: Improvements to --init-from-dash

Adds user-specified CPU limit to wrangler.toml if one exists. Excludes usage_model from wrangler.toml in all cases, since this field is deprecated and no longer used.
#5553 dcd65dd Thanks @rozenmd! - fix: refactor d1's time-travel compatibility check
#5380 57d5658 Thanks @GregBrimble! - fix: Respect --no-bundle when deploying a _worker.js/ directory in Pages projects
#5536 a7aa28a Thanks @Cherry! - fix: resolve a regression where wrangler pages dev would bind to port 8787 by default instead of 8788 since wrangler@3.38.0
Updated dependencies [9575a51]:
- miniflare@3.20240405.0

`v3.48.0`

Compare Source

Minor Changes

#5429 c5561b7 Thanks @ocsfrank! - R2 will introduce storage classes soon. Wrangler allows you to interact with storage classes once it is
enabled on your account.

Wrangler supports an -s flag that allows the user to specify a storage class when creating a bucket,
changing the default storage class of a bucket, and uploading an object.
```
wrangler r2 bucket create ia-bucket -s InfrequentAccess
wrangler r2 bucket update storage-class my-bucket -s InfrequentAccess
wrangler r2 object put bucket/ia-object -s InfrequentAccess --file foo
```

Patch Changes

#5531 887150a Thanks @penalosa! - fix: Write wrangler pages functions build-env to file rather than stdout
#5526 bafbd67 Thanks [@rozenmd](https://to

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 · 2024-05-08T02:10:42Z

⚠ 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/unsupported-edge-error/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/unsupported-edge-error

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

.                                        |  WARN  Ignoring broken lockfile at /tmp/renovate/repos/github/prisma/prisma/packages/client/tests/e2e/schema-not-found-sst-electron: Lockfile /tmp/renovate/repos/github/prisma/prisma/packages/client/tests/e2e/schema-not-found-sst-electron/pnpm-lock.yaml not compatible with current pnpm
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



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

File name: packages/client/tests/e2e/require-in-the-middle/pnpm-lock.yaml

.                                        |  WARN  Ignoring broken lockfile at /tmp/renovate/repos/github/prisma/prisma/packages/client/tests/e2e/require-in-the-middle: Lockfile /tmp/renovate/repos/github/prisma/prisma/packages/client/tests/e2e/require-in-the-middle/pnpm-lock.yaml not compatible with current pnpm
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



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

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/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

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

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

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

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

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

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



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

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



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

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

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

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



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

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

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/generator-config-types/pnpm-lock.yaml

.                                        |  WARN  Ignoring broken lockfile at /tmp/renovate/repos/github/prisma/prisma/packages/client/tests/e2e/generator-config-types: Lockfile /tmp/renovate/repos/github/prisma/prisma/packages/client/tests/e2e/generator-config-types/pnpm-lock.yaml not compatible with current pnpm
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/generator-config-types

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



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

File name: packages/client/tests/e2e/enum-import-in-edge/pnpm-lock.yaml

.                                        |  WARN  Ignoring broken lockfile at /tmp/renovate/repos/github/prisma/prisma/packages/client/tests/e2e/enum-import-in-edge: Lockfile /tmp/renovate/repos/github/prisma/prisma/packages/client/tests/e2e/enum-import-in-edge/pnpm-lock.yaml not compatible with current pnpm
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



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

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

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

.                                        |  WARN  Ignoring broken lockfile at /tmp/renovate/repos/github/prisma/prisma/packages/client/tests/e2e/driver-adapters-accelerate: Lockfile /tmp/renovate/repos/github/prisma/prisma/packages/client/tests/e2e/driver-adapters-accelerate/pnpm-lock.yaml not compatible with current pnpm
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

.                                        |  WARN  Ignoring broken lockfile at /tmp/renovate/repos/github/prisma/prisma/packages/client/tests/e2e/connection-limit-reached: Lockfile /tmp/renovate/repos/github/prisma/prisma/packages/client/tests/e2e/connection-limit-reached/pnpm-lock.yaml not compatible with current pnpm
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

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



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

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

socket-security · 2024-05-08T02:12:21Z

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@prisma/extension-accelerate@0.5.0	None	`0`	47.6 kB	prismabot
npm/@types/jest@29.5.11	Transitive: environment, filesystem, unsafe	`+48`	1.75 MB	types
npm/@types/jest@29.5.12	Transitive: environment	`+18`	854 kB	types
npm/@types/node@16.18.65	None	`0`	3.51 MB	types
npm/@types/node@16.18.82	None	`0`	3.55 MB	types
npm/@types/node@16.18.97	None	`0`	1.8 MB	types
npm/esbuild@0.20.0	environment, filesystem, network, shell	`0`	134 kB	evanw
npm/expect-type@0.16.0	None	`0`	39.9 kB	mmkale
npm/wrangler@3.28.2	Transitive: environment, filesystem, network, shell, unsafe	`+61`	20 MB	wrangler-publisher
npm/wrangler@3.5.1	Transitive: environment, filesystem, network, shell, unsafe	`+55`	19.5 MB	wrangler-publisher

🚮 Removed packages: npm/esbuild@0.18.17, npm/expect-type@0.19.0, npm/webpack@5.75.0

View full report↗︎

github-actions · 2024-05-08T02:14:40Z

size-limit report 📦

Path	Size
packages/client/runtime/library.js	179.82 KB (0%)
packages/client/runtime/library.d.ts	81 B (0%)
packages/client/runtime/binary.js	600.89 KB (0%)
packages/client/runtime/binary.d.ts	26 B (0%)
packages/client/runtime/edge.js	159.01 KB (0%)
packages/client/runtime/edge-esm.js	158.91 KB (0%)
packages/client/runtime/wasm.js	114.9 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.02 MB (0%)
packages/cli/prisma-0.0.0.tgz	3.73 MB (0%)
packages/bundle-size/da-workers-libsql/output.tgz	888.08 KB (0%)
packages/bundle-size/da-workers-neon/output.tgz	967.18 KB (0%)
packages/bundle-size/da-workers-pg/output.tgz	985.75 KB (0%)
packages/bundle-size/da-workers-pg-worker/output.tgz	941.47 KB (0%)
packages/bundle-size/da-workers-planetscale/output.tgz	902.5 KB (0%)
packages/bundle-size/da-workers-d1/output.tgz	861.15 KB (0%)

renovate · 2024-05-15T05:27:13Z

⚠️ 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/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

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

.                                        |  WARN  Ignoring broken lockfile at /tmp/renovate/repos/github/prisma/prisma/packages/client/tests/e2e/schema-not-found-sst-electron: Lockfile /tmp/renovate/repos/github/prisma/prisma/packages/client/tests/e2e/schema-not-found-sst-electron/pnpm-lock.yaml not compatible with current pnpm
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

.                                        |  WARN  Ignoring broken lockfile at /tmp/renovate/repos/github/prisma/prisma/packages/client/tests/e2e/require-in-the-middle: Lockfile /tmp/renovate/repos/github/prisma/prisma/packages/client/tests/e2e/require-in-the-middle/pnpm-lock.yaml not compatible with current pnpm
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/prisma-client-imports/pnpm-lock.yaml

.                                        |  WARN  Ignoring broken lockfile at /tmp/renovate/repos/github/prisma/prisma/packages/client/tests/e2e/prisma-client-imports: Lockfile /tmp/renovate/repos/github/prisma/prisma/packages/client/tests/e2e/prisma-client-imports/pnpm-lock.yaml not compatible with current pnpm
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

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

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

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

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

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

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

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



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/14_monorepo-serverComponents-customOutput-reExportDirect/packages/db

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

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/mongodb-notablescan/pnpm-lock.yaml

.                                        |  WARN  Ignoring broken lockfile at /tmp/renovate/repos/github/prisma/prisma/packages/client/tests/e2e/mongodb-notablescan: Lockfile /tmp/renovate/repos/github/prisma/prisma/packages/client/tests/e2e/mongodb-notablescan/pnpm-lock.yaml not compatible with current pnpm
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/mongodb-notablescan

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

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/generator-config-types/pnpm-lock.yaml

.                                        |  WARN  Ignoring broken lockfile at /tmp/renovate/repos/github/prisma/prisma/packages/client/tests/e2e/generator-config-types: Lockfile /tmp/renovate/repos/github/prisma/prisma/packages/client/tests/e2e/generator-config-types/pnpm-lock.yaml not compatible with current pnpm
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/generator-config-types

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

.                                        |  WARN  Ignoring broken lockfile at /tmp/renovate/repos/github/prisma/prisma/packages/client/tests/e2e/enum-import-in-edge: Lockfile /tmp/renovate/repos/github/prisma/prisma/packages/client/tests/e2e/enum-import-in-edge/pnpm-lock.yaml not compatible with current pnpm
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

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

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

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

.                                        |  WARN  Ignoring broken lockfile at /tmp/renovate/repos/github/prisma/prisma/packages/client/tests/e2e/driver-adapters-accelerate: Lockfile /tmp/renovate/repos/github/prisma/prisma/packages/client/tests/e2e/driver-adapters-accelerate/pnpm-lock.yaml not compatible with current pnpm
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

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

.                                        |  WARN  Ignoring broken lockfile at /tmp/renovate/repos/github/prisma/prisma/packages/client/tests/e2e/connection-limit-reached: Lockfile /tmp/renovate/repos/github/prisma/prisma/packages/client/tests/e2e/connection-limit-reached/pnpm-lock.yaml not compatible with current pnpm
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

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

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

socket-security · 2024-05-15T05:27:54Z

🚨 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	Note	Source
Install scripts	npm/workerd@1.20230814.1	Install script: postinstall Source: `node install.js`	`packages/client/tests/e2e/unsupported-edge-error/tests/pnpm-lock.yaml`
Install scripts	npm/workerd@1.20240129.0	Install script: postinstall Source: `node install.js`	`packages/client/tests/e2e/unsupported-browser-error/package.json` `packages/client/tests/e2e/unsupported-browser-error/pnpm-lock.yaml`

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
@SocketSecurity ignore npm/workerd@1.20240129.0

codspeed-hq · 2024-05-22T06:17:51Z

CodSpeed Performance Report

Merging #24108 will not alter performance

_{Comparing renovate/e2e-tests (95c37c8) with main (1e26197)}

Summary

✅ 3 untouched benchmarks

I added a Renovate rule to make the mysql image update separate from, for example #24108 See https://docs.renovatebot.com/docker/

renovate bot requested a review from a team as a code owner May 8, 2024 02:10

renovate bot requested review from Jolg42 and jkomyno and removed request for a team May 8, 2024 02:10

renovate bot requested a review from SevInf May 8, 2024 02:10

renovate bot force-pushed the renovate/e2e-tests branch from 52799d8 to 0d8e7c3 Compare May 15, 2024 05:27

renovate bot force-pushed the renovate/e2e-tests branch from 0d8e7c3 to 4d18fb8 Compare May 22, 2024 06:06

Jolg42 added a commit that referenced this pull request May 22, 2024

test(client/e2e): use mysql:lts image

86937cc

I added a Renovate rule to make the mysql image update separate from, for example #24108 See https://docs.renovatebot.com/docker/

Jolg42 mentioned this pull request May 22, 2024

test(client/e2e): use mysql:lts image #24260

Merged

chore(deps): update e2e tests

95c37c8

renovate bot force-pushed the renovate/e2e-tests branch from 4d18fb8 to 95c37c8 Compare May 22, 2024 15:09

Jolg42 merged commit b77b06d into main May 22, 2024
202 of 205 checks passed

Jolg42 deleted the renovate/e2e-tests branch May 22, 2024 16:22

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

chore(deps): update e2e tests #24108

chore(deps): update e2e tests #24108

renovate bot commented May 8, 2024 •

edited

renovate bot commented May 8, 2024

socket-security bot commented May 8, 2024 •

edited

github-actions bot commented May 8, 2024 •

edited

renovate bot commented May 15, 2024 •

edited

socket-security bot commented May 15, 2024 •

edited

codspeed-hq bot commented May 22, 2024 •

edited

chore(deps): update e2e tests #24108

chore(deps): update e2e tests #24108

Conversation

renovate bot commented May 8, 2024 • edited

Release Notes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Configuration

renovate bot commented May 8, 2024

⚠ Artifact update problem

File name: packages/client/tests/e2e/unsupported-edge-error/pnpm-lock.yaml

File name: packages/client/tests/e2e/unsupported-browser-error/pnpm-lock.yaml

File name: packages/client/tests/e2e/schema-not-found-sst-electron/pnpm-lock.yaml

File name: packages/client/tests/e2e/require-in-the-middle/pnpm-lock.yaml

File name: packages/client/tests/e2e/publish-extensions/pnpm-lock.yaml

File name: packages/client/tests/e2e/prisma-client-imports/pnpm-lock.yaml

File name: packages/client/tests/e2e/pg-self-signed-cert-error/pnpm-lock.yaml

File name: packages/client/tests/e2e/noengine-file-deletion/pnpm-lock.yaml

File name: packages/client/tests/e2e/nextjs-schema-not-found/9_monorepo-noServerComponents-customOutput-noReExport/pnpm-lock.yaml

File name: packages/client/tests/e2e/nextjs-schema-not-found/8_monorepo-serverComponents-noCustomOutput-noReExport/pnpm-lock.yaml

File name: packages/client/tests/e2e/nextjs-schema-not-found/7_monorepo-noServerComponents-noCustomOutput-noReExport/pnpm-lock.yaml

File name: packages/client/tests/e2e/nextjs-schema-not-found/6_simplerepo-serverComponents-customOutput-noReExport/pnpm-lock.yaml

File name: packages/client/tests/e2e/nextjs-schema-not-found/5_simplerepo-noServerComponents-customOutput-noReExport/pnpm-lock.yaml

File name: packages/client/tests/e2e/nextjs-schema-not-found/4_simplerepo-serverComponents-noCustomOutput-noReExport/pnpm-lock.yaml

File name: packages/client/tests/e2e/nextjs-schema-not-found/3_simplerepo-noServerComponents-noCustomOutput-noReExport/pnpm-lock.yaml

File name: packages/client/tests/e2e/nextjs-schema-not-found/18_monorepo-serverComponents-customOutput-reExportIndirect-ts/pnpm-lock.yaml

File name: packages/client/tests/e2e/nextjs-schema-not-found/17_monorepo-noServerComponents-customOutput-reExportIndirect-ts/pnpm-lock.yaml

File name: packages/client/tests/e2e/nextjs-schema-not-found/16_monorepo-serverComponents-customOutput-reExportIndirect/pnpm-lock.yaml

File name: packages/client/tests/e2e/nextjs-schema-not-found/15_monorepo-noServerComponents-customOutput-reExportIndirect/pnpm-lock.yaml

File name: packages/client/tests/e2e/nextjs-schema-not-found/14_monorepo-serverComponents-customOutput-reExportDirect/pnpm-lock.yaml

File name: packages/client/tests/e2e/nextjs-schema-not-found/13_monorepo-noServerComponents-customOutput-reExportDirect/pnpm-lock.yaml

File name: packages/client/tests/e2e/nextjs-schema-not-found/12_monorepo-serverComponents-noCustomOutput-reExportIndirect/pnpm-lock.yaml

File name: packages/client/tests/e2e/nextjs-schema-not-found/11_monorepo-noServerComponents-noCustomOutput-reExportIndirect/pnpm-lock.yaml

File name: packages/client/tests/e2e/nextjs-schema-not-found/10_monorepo-serverComponents-customOutput-noReExport/pnpm-lock.yaml

File name: packages/client/tests/e2e/issues/19999-tsc-extensions-oom/pnpm-lock.yaml

File name: packages/client/tests/e2e/issues/19866-ts-composite-declaration/pnpm-lock.yaml

File name: packages/client/tests/e2e/invalid-package-version/pnpm-lock.yaml

File name: packages/client/tests/e2e/generator-config-types/pnpm-lock.yaml

File name: packages/client/tests/e2e/example/pnpm-lock.yaml

File name: packages/client/tests/e2e/enum-import-in-edge/pnpm-lock.yaml

File name: packages/client/tests/e2e/engine-not-found-error/tooling-tampered-with-engine-copy/pnpm-lock.yaml

File name: packages/client/tests/e2e/engine-not-found-error/native-generated-different-platform/pnpm-lock.yaml

File name: packages/client/tests/e2e/engine-not-found-error/bundler-tampered-with-engine-copy/pnpm-lock.yaml

File name: packages/client/tests/e2e/engine-not-found-error/binary-targets-incorrectly-pinned/pnpm-lock.yaml

File name: packages/client/tests/e2e/driver-adapters-accelerate/pnpm-lock.yaml

File name: packages/client/tests/e2e/default-version/pnpm-lock.yaml

File name: packages/client/tests/e2e/connection-limit-reached/pnpm-lock.yaml

File name: packages/client/tests/e2e/bundler-detection-error/pnpm-lock.yaml

File name: packages/client/tests/e2e/browser-unsupported-errors/pnpm-lock.yaml

File name: packages/client/tests/e2e/adapter-d1-itx-error/pnpm-lock.yaml

File name: packages/client/tests/e2e/accelerate-types/pnpm-lock.yaml

socket-security bot commented May 8, 2024 • edited

github-actions bot commented May 8, 2024 • edited

size-limit report 📦

renovate bot commented May 15, 2024 • edited

⚠️ Artifact update problem

File name: packages/client/tests/e2e/unsupported-edge-error/pnpm-lock.yaml

File name: packages/client/tests/e2e/unsupported-browser-error/pnpm-lock.yaml

File name: packages/client/tests/e2e/schema-not-found-sst-electron/pnpm-lock.yaml

File name: packages/client/tests/e2e/require-in-the-middle/pnpm-lock.yaml

File name: packages/client/tests/e2e/publish-extensions/pnpm-lock.yaml

renovate bot commented May 8, 2024 •

edited

socket-security bot commented May 8, 2024 •

edited

github-actions bot commented May 8, 2024 •

edited

renovate bot commented May 15, 2024 •

edited

socket-security bot commented May 15, 2024 •

edited

codspeed-hq bot commented May 22, 2024 •

edited