fix(deps): update dependency eslint-plugin-promise to v7

[tradeshift-renovate]

This PR contains the following updates:

Package	Type	Update	Change
eslint-plugin-promise	dependencies	major	^6.0.0 -> ^7.0.0

---

Release Notes

eslint-community/eslint-plugin-promise (eslint-plugin-promise)

v7.0.0

Compare Source

• feat!: Update node versions to align with eslint v9 (#​505) (09d0650), closes #​505 /github.com/eslint-community/eslint-plugin-promise/pull/484#issuecomment-2246887433 eslint-community/eslint-plugin-promise#504

BREAKING CHANGES

• Requires Node.js: ^18.18.0 || ^20.9.0 || >=21.1.0

v6.6.0

Compare Source

Bug Fixes

• always-return: treat process.exit() or process.abort() as an acceptable "return" (#​493) (f368c5a)

Features

• add strict option to disallow then or catch following await or yield (#​494) (fa482cc)

v6.5.1

Compare Source

Bug Fixes

• remove name from eslintrc config; fixes #​489 (#​490) (c011a1a)

v6.5.0

Compare Source

Features

• add name property to configs (for use with tooling) (#​486) (ca9e9b4)

v6.4.0

Compare Source

Features

• add support for flat config (#​479) (ecbce9f)

v6.3.0

Compare Source

Features

• add support for eslint v9 (#​478) (4dfc8a7)

---

Configuration

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

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

♻️ 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: [email protected]
npm error Found: [email protected]
npm error node_modules/eslint-plugin-promise
npm error   eslint-plugin-promise@"^7.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer eslint-plugin-promise@"^6.0.0" from [email protected]
npm error node_modules/eslint-config-standard
npm error   eslint-config-standard@"^17.0.0-0 || ^17" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/eslint-plugin-promise
npm error   peer eslint-plugin-promise@"^6.0.0" from [email protected]
npm error   node_modules/eslint-config-standard
npm error     eslint-config-standard@"^17.0.0-0 || ^17" 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-07-26T05_33_58_334Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-07-26T05_33_58_334Z-debug-0.log