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.

Sign up for GitHub

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

Jump to bottom

chore(deps): update all minor dependencies (minor) #5479

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from
Open

chore(deps): update all minor dependencies (minor) #5479

wants to merge 1 commit into from
+11 −11

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 22, 2024 •
edited

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence Type Update
@applitools/eyes-cypress 3.43.1 -> 3.44.2 age adoption passing confidence devDependencies minor
@cspell/eslint-plugin (source) 8.7.0 -> 8.8.1 age adoption passing confidence devDependencies minor
@typescript-eslint/eslint-plugin (source) 7.6.0 -> 7.9.0 age adoption passing confidence devDependencies minor
@typescript-eslint/parser (source) 7.6.0 -> 7.9.0 age adoption passing confidence devDependencies minor
@unocss/reset ^0.59.0 -> ^0.60.0 age adoption passing confidence devDependencies minor
@vite-pwa/vitepress ^0.4.0 -> ^0.5.0 age adoption passing confidence devDependencies minor
@vitest/coverage-v8 (source) 1.5.3 -> 1.6.0 age adoption passing confidence devDependencies minor
@vitest/spy (source) 1.5.3 -> 1.6.0 age adoption passing confidence devDependencies minor
@vitest/ui (source) 1.5.3 -> 1.6.0 age adoption passing confidence devDependencies minor
@zenuml/core 3.21.2 -> 3.23.3 age adoption passing confidence dependencies minor
ajv (source) 8.12.0 -> 8.13.0 age adoption passing confidence devDependencies minor
cspell (source) 8.7.0 -> 8.8.1 age adoption passing confidence devDependencies minor
cypress (source) 13.7.3 -> 13.9.0 age adoption passing confidence devDependencies minor
cypress/included 13.7.3 -> 13.9.0 age adoption passing confidence minor
cytoscape (source) 3.28.1 -> 3.29.2 age adoption passing confidence dependencies minor
esbuild ^0.20.2 -> ^0.21.0 age adoption passing confidence devDependencies minor
lycheeverse/lychee-action v1.9.3 -> v1.10.0 age adoption passing confidence action minor
node (source) 20.12.2 -> 20.13.1 age adoption passing confidence minor
node 20.12.2-alpine3.19 -> 20.13.1-alpine3.19 age adoption passing confidence final minor
tsx 4.7.3 -> 4.10.5 age adoption passing confidence devDependencies minor
type-fest 4.15.0 -> 4.18.2 age adoption passing confidence devDependencies minor
unocss ^0.59.0 -> ^0.60.0 age adoption passing confidence devDependencies minor
unplugin-vue-components ^0.26.0 -> ^0.27.0 age adoption passing confidence devDependencies minor
vite-plugin-pwa ^0.19.7 -> ^0.20.0 age adoption passing confidence devDependencies minor
vitepress (source) 1.1.4 -> 1.2.0 age adoption passing confidence devDependencies minor
vitest (source) 1.5.3 -> 1.6.0 age adoption passing confidence devDependencies minor
workbox-window (source) 7.0.0 -> 7.1.0 age adoption passing confidence devDependencies minor

Release Notes

streetsidesoftware/cspell (@​cspell/eslint-plugin)

v8.8.1

Compare Source

  • chore: Do not stop update if it fails to lint. (64ba085)

v8.8.0

Compare Source

Note: Version bump only for package @​cspell/eslint-plugin

typescript-eslint/typescript-eslint (@​typescript-eslint/eslint-plugin)

v7.9.0

Compare Source

🩹 Fixes
  • eslint-plugin: [explicit-function-return-types] fix false positive on default parameters
❤️ Thank You
  • Kirk Waiblinger
  • Sheetal Nandi
  • Vinccool96

You can read about our versioning strategy and releases on our website.

v7.8.0

Compare Source

🩹 Fixes

  • eslint-plugin: [no-unsafe-argument] handle tagged templates

  • eslint-plugin: [prefer-optional-chain] suggests optional chaining during strict null equality check

  • eslint-plugin: [consistent-type-assertions] handle tagged templates

  • eslint-plugin: [no-unsafe-return] handle union types

  • eslint-plugin: [no-unused-vars] clear error report range

❤️ Thank You
  • auvred
  • Josh Goldberg ✨
  • jsfm01
  • Kim Sang Du
  • YeonJuan

You can read about our versioning strategy and releases on our website.

v7.7.1

Compare Source

🩹 Fixes

  • eslint-plugin: [no-unsafe-assignment] handle shorthand property assignment

  • eslint-plugin: [explicit-function-return-type] fix checking wrong ancestor's return type

  • eslint-plugin: [prefer-optional-chain] only look at left operand for requireNullish

  • eslint-plugin: [no-for-in-array] refine report location

  • eslint-plugin: [no-unnecessary-type-assertion] allow non-null assertion for void type

❤️ Thank You
  • Abraham Guo
  • Kirk Waiblinger
  • YeonJuan

You can read about our versioning strategy and releases on our website.

v7.7.0

Compare Source

🚀 Features
  • eslint-plugin: replace no-new-symbol with no-new-native-nonconstructor
❤️ Thank You
  • Dave
  • Josh Goldberg ✨

You can read about our versioning strategy and releases on our website.

typescript-eslint/typescript-eslint (@​typescript-eslint/parser)

v7.9.0

Compare Source

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

v7.8.0

Compare Source

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

v7.7.1

Compare Source

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

v7.7.0

Compare Source

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

unocss/unocss (@​unocss/reset)

v0.60.2

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v0.60.1

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.60.0

Compare Source

   🚨 Breaking Changes
   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub
vite-pwa/vitepress (@​vite-pwa/vitepress)

v0.5.0

Compare Source

   🚨 Breaking Changes
    View changes on GitHub
vitest-dev/vitest (@​vitest/coverage-v8)

v1.6.0

Compare Source

   🚀 Features
   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub
mermaid-js/zenuml-core (@​zenuml/core)

v3.23.3

Compare Source

v3.23.2

Compare Source

v3.23.1

Compare Source

v3.23.0

Compare Source

v3.22.1

Compare Source

v3.22.0

Compare Source

ajv-validator/ajv (ajv)

v8.13.0

Compare Source

  • add named exports
  • update dependencies
  • update node.js
streetsidesoftware/cspell (cspell)

v8.8.1

Compare Source

  • chore: Do not stop update if it fails to lint. (64ba085)

v8.8.0

Compare Source

Note: Version bump only for package cspell

cypress-io/cypress (cypress)

v13.9.0

Compare Source

Changelog: https://docs.cypress.io/guides/references/changelog#13-9-0

v13.8.1

Compare Source

Changelog: https://docs.cypress.io/guides/references/changelog#13-8-1

v13.8.0

Compare Source

Changelog: https://docs.cypress.io/guides/references/changelog#13-8-0

cytoscape/cytoscape.js (cytoscape)

v3.29.2

Compare Source

Release version v3.29.2

v3.29.1

Compare Source

Release version v3.29.1

v3.29.0

Compare Source

Release version v3.29.0

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 {
  @​track foo = 1
  @​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 {
  @​(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 { @​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: /* @​__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 {
  @​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() {}
lycheeverse/lychee-action (lycheeverse/lychee-action)

v1.10.0

Compare Source

What's Changed

New Contributors

Full Changelog: lycheeverse/lychee-action@v1.9.3...v1.10.0

nodejs/node (node)

v20.13.1: 2024-05-09, Version 20.13.1 'Iron' (LTS), @​marco-ippolito

Compare Source

2024-05-09, Version 20.13.1 'Iron' (LTS), @​marco-ippolito

Revert "tools: install npm PowerShell scripts on Windows"

Due to a regression in the npm installation on Windows, this commit reverts the change that installed npm PowerShell scripts on Windows.

Commits
  • [b7d80802cc] - Revert "tools: install npm PowerShell scripts on Windows" (marco-ippolito) #​52897

v20.13.0

Compare Source

privatenumbe

Configuration

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

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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
Copy link
Contributor Author

renovate bot commented Apr 22, 2024 •
edited

⚠ Artifact update problem

Renovate failed to update an artifact 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: pnpm-lock.yaml
Scope: all 8 workspace projects
Progress: resolved 1, reused 0, downloaded 0, added 0
packages/mermaid                         |  WARN  deprecated @types/[email protected]
Progress: resolved 59, reused 52, downloaded 0, added 0
Progress: resolved 128, reused 116, downloaded 1, added 0
Progress: resolved 128, reused 116, downloaded 3, added 0
Progress: resolved 130, reused 116, downloaded 8, added 0
Progress: resolved 191, reused 161, downloaded 12, added 0
Progress: resolved 215, reused 172, downloaded 12, added 0
Progress: resolved 355, reused 308, downloaded 12, added 0
Progress: resolved 477, reused 422, downloaded 12, added 0
Progress: resolved 639, reused 596, downloaded 12, added 0
Progress: resolved 657, reused 614, downloaded 14, added 0
Progress: resolved 892, reused 856, downloaded 14, added 0
Progress: resolved 1034, reused 1000, downloaded 16, added 0
Progress: resolved 1154, reused 1114, downloaded 19, added 0
Progress: resolved 1262, reused 1198, downloaded 26, added 0
Progress: resolved 1361, reused 1260, downloaded 36, added 0
Progress: resolved 1454, reused 1343, downloaded 45, added 0
Progress: resolved 1486, reused 1363, downloaded 57, added 0
Progress: resolved 1538, reused 1408, downloaded 62, added 0
Progress: resolved 1622, reused 1493, downloaded 63, added 0
Progress: resolved 1640, reused 1511, downloaded 66, added 0
Progress: resolved 1670, reused 1539, downloaded 67, added 0
Progress: resolved 1731, reused 1594, downloaded 74, added 0
Progress: resolved 1794, reused 1654, downloaded 79, added 0
Progress: resolved 1834, reused 1693, downloaded 81, added 0
Progress: resolved 1906, reused 1766, downloaded 81, added 0
Progress: resolved 1966, reused 1824, downloaded 81, added 0
 ERR_PNPM_PATCH_NOT_APPLIED  The following patches were not applied: [email protected]

Either remove them from "patchedDependencies" or update them to match packages in your dependencies.

@netlify Netlify
Copy link

netlify bot commented Apr 22, 2024 •
edited

❌ Deploy Preview for mermaid-js failed.

Name Link
🔨 Latest commit 3def21a
🔍 Latest deploy log https://app.netlify.com/sites/mermaid-js/deploys/6648ae3e99c6d5000819c78a

@codecov Codecov
Copy link

codecov bot commented Apr 22, 2024 •
edited

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 5.72%. Comparing base (7bcba29) to head (d0e5599).

❗ Current head d0e5599 differs from pull request most recent head 3def21a

Please upload reports for the commit 3def21a to get more accurate results.

Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##           develop   #5479      +/-   ##
==========================================
- Coverage     5.73%   5.72%   -0.01%     
==========================================
  Files          277     278       +1     
  Lines        41988   42013      +25     
  Branches       515     490      -25     
==========================================
- Hits          2409    2407       -2     
- Misses       39579   39606      +27
Flag Coverage Δ
unit 5.72% <ø> (-0.01%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

see 20 files with indirect coverage changes

@renovate renovate bot force-pushed the renovate/all-minor branch 6 times, most recently from d0e5599 to 92330db Compare April 30, 2024 14:09
@renovate renovate bot force-pushed the renovate/all-minor branch 10 times, most recently from f8eaaf7 to e0bfece Compare May 8, 2024 06:37
@renovate renovate bot force-pushed the renovate/all-minor branch 3 times, most recently from b5b96a8 to 1bd9167 Compare May 9, 2024 15:48
@renovate Renovate
Copy link
Contributor Author

renovate bot commented May 9, 2024 •
edited

⚠️ Artifact update problem

Renovate failed to update an artifact 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: pnpm-lock.yaml
Scope: all 8 workspace projects
Progress: resolved 1, reused 0, downloaded 0, added 0
packages/mermaid                         |  WARN  deprecated @types/[email protected]
Progress: resolved 80, reused 73, downloaded 0, added 0
Progress: resolved 127, reused 116, downloaded 3, added 0
Progress: resolved 129, reused 116, downloaded 6, added 0
Progress: resolved 130, reused 116, downloaded 12, added 0
Progress: resolved 193, reused 171, downloaded 13, added 0
Progress: resolved 445, reused 410, downloaded 13, added 0
Progress: resolved 617, reused 588, downloaded 14, added 0
Progress: resolved 953, reused 927, downloaded 14, added 0
Progress: resolved 1169, reused 1150, downloaded 14, added 0
Progress: resolved 1281, reused 1258, downloaded 15, added 0
Progress: resolved 1316, reused 1290, downloaded 23, added 0
Progress: resolved 1335, reused 1300, downloaded 31, added 0
Progress: resolved 1405, reused 1341, downloaded 39, added 0
Progress: resolved 1476, reused 1367, downloaded 46, added 0
Progress: resolved 1503, reused 1380, downloaded 60, added 0
Progress: resolved 1582, reused 1452, downloaded 67, added 0
Progress: resolved 1648, reused 1511, downloaded 69, added 0
Progress: resolved 1718, reused 1563, downloaded 78, added 0
Progress: resolved 1767, reused 1624, downloaded 84, added 0
Progress: resolved 1811, reused 1668, downloaded 84, added 0
Progress: resolved 1895, reused 1752, downloaded 84, added 0
Progress: resolved 1940, reused 1796, downloaded 84, added 0
 ERR_PNPM_PATCH_NOT_APPLIED  The following patches were not applied: [email protected]

Either remove them from "patchedDependencies" or update them to match packages in your dependencies.

@renovate renovate bot force-pushed the renovate/all-minor branch 6 times, most recently from ed742d0 to bce04b0 Compare May 16, 2024 08:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
0 participants