chore(deps): update dependency @rollup/plugin-commonjs to v26 - autoclosed

[tradeshift-renovate]

This PR contains the following updates:

Package	Type	Update	Change
@rollup/plugin-commonjs (source)	devDependencies	major	^25.0.0 -> ^26.0.1

---

Release Notes

rollup/plugins (@​rollup/plugin-commonjs)

v26.0.1

2024-06-05

Bugfixes

• fix: correct import of glob (04a15b5)

v26.0.0

2024-06-05

Breaking Changes

• chore!: bump glob's version (#​1695)

v25.0.8

2024-05-22

Bugfixes

• fix: preserve the class body property keys even if they are special keywords (#​1688)

v25.0.7

Compare Source

2023-10-15

Bugfixes

• fix: bump magic-string version #​1596

v25.0.6

Compare Source

2023-10-15

Bugfixes

• fix: Keep the shebang at the top of the file content #​1610

v25.0.5

Compare Source

2023-10-05

Bugfixes

• fix: ensure rollup 4 compatibility #​1595

v25.0.4

Compare Source

2023-08-11

Updates

• docs: update docs #​1545

v25.0.3

Compare Source

2023-07-15

Bugfixes

• fix: preserve this reference in the child class #​1537

v25.0.2

Compare Source

2023-06-19

Bugfixes

• fix: add classBodyDepth flag #​1507

v25.0.1

Compare Source

2023-06-10

Bugfixes

• fix: change dynamicRequireRoot to normalizedDynamicRequireRoot && tweak related tests #​1508

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻️ Rebasing: Never, 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 Renovate Bot.

[tradeshift-renovate]

⚠️ 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: package-lock.json

npm warn config cert `key` and `cert` are no longer used for most registry operations.
npm warn config Use registry scoped `keyfile` and `certfile` instead.
npm warn config       Example:
npm warn config       //other-registry.tld/:keyfile=/path/to/key.pem
npm warn config       //other-registry.tld/:certfile=/path/to/cert.crt
npm warn config key `key` and `cert` are no longer used for most registry operations.
npm warn config Use registry scoped `keyfile` and `certfile` instead.
npm warn config       Example:
npm warn config       //other-registry.tld/:keyfile=/path/to/key.pem
npm warn config       //other-registry.tld/:certfile=/path/to/cert.crt
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @rollup/[email protected]
npm error Found: [email protected]
npm error node_modules/rollup
npm error   dev rollup@"^4.0.0" from the root project
npm error   peerOptional rollup@"^1.20.0||^2.0.0||^3.0.0||^4.0.0" from @rollup/[email protected]
npm error   node_modules/@rollup/plugin-json
npm error     dev @rollup/plugin-json@"^6.0.0" from the root project
npm error   3 more (@rollup/plugin-node-resolve, @rollup/pluginutils, @rollup/plugin-commonjs)
npm error
npm error Could not resolve dependency:
npm error peerOptional rollup@"^1.20.0||^2.0.0||^3.0.0" from @rollup/[email protected]
npm error node_modules/@rollup/plugin-babel
npm error   dev @rollup/plugin-babel@"^6.0.3" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/rollup
npm error   peerOptional rollup@"^1.20.0||^2.0.0||^3.0.0" from @rollup/[email protected]
npm error   node_modules/@rollup/plugin-babel
npm error     dev @rollup/plugin-babel@"^6.0.3" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2024-06-06T20_32_42_961Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-06-06T20_32_42_961Z-debug-0.log