chore(deps): update dependency eslint-plugin-promise to v6

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
eslint-plugin-promise	5.1.0 -> 6.1.1

---

Release Notes

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

v6.1.1

Compare Source

Bug Fixes

• no-multiple-resolved: false positives when the last expression in a try block is a call to resolve (#​384) (dc51b1c)

v6.1.0

Compare Source

Bug Fixes

• always-return: false positives for logical expr (#​363) (a60d1cb)
• CI: fix release script (#​380) (71e53a0)
• minor typos (#​359) (b431e46)
• no-nesting: nested references vars in closure (#​361) (08052e8)
• update repo link (#​349) (3906810)

Features

• add no-multiple-resolved rule (#​369) (3a6fdbe)
• always-return: add ignoreLastCallback option (#​365) (01def31)
• catch-or-return,no-new-statics,no-promise-in-callback,valid-params: add support for Promise.allSettled() & Promise.any() (#​370) (e080f82)
• param-names: add resolvePattern & rejectPattern option (#​368) (df25e3c)

v6.0.1

Compare Source

• Fixed @​typescript-eslint/parser issue #​331, #​205

v6.0.0

Compare Source

• Dropped node 10 from engines #​231
• Updated a ton of deps #​236, #​237, #​235, #​234
• ESLint 8 support #​219

v5.2.0

Compare Source

• Updated param-names rule to allow for unused params

v5.1.1

Compare Source

• Updated docs to include no-callback-in-promise reasons #​215

---

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: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• 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]

⚠ 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 ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: eslint-config-standard@16.0.3
npm ERR! Found: eslint@8.1.0
npm ERR! node_modules/eslint
npm ERR!   dev eslint@"8.1.0" from the root project
npm ERR!   peer eslint@"^7.5.0 || ^8.0.0" from @babel/eslint-parser@7.17.0
npm ERR!   node_modules/@babel/eslint-parser
npm ERR!     dev @babel/eslint-parser@"7.17.0" from the root project
npm ERR!   6 more (eslint-plugin-import, eslint-plugin-node, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer eslint@"^7.12.1" from eslint-config-standard@16.0.3
npm ERR! node_modules/eslint-config-standard
npm ERR!   dev eslint-config-standard@"16.0.3" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: eslint@7.32.0
npm ERR! node_modules/eslint
npm ERR!   peer eslint@"^7.12.1" from eslint-config-standard@16.0.3
npm ERR!   node_modules/eslint-config-standard
npm ERR!     dev eslint-config-standard@"16.0.3" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! 
npm ERR! For a full report see:
npm ERR! /tmp/renovate-cache/others/npm/_logs/2022-11-20T13_04_57_531Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate-cache/others/npm/_logs/2022-11-20T13_04_57_531Z-debug-0.log

[codecov-commenter]

Codecov Report

Base: 100.00% // Head: 100.00% // No change to project coverage 👍

Coverage data is based on head (2a265ec) compared to base (8b06833).
Patch has no changes to coverable lines.

❗ Current head 2a265ec differs from pull request most recent head 6a80baf. Consider uploading reports for the commit 6a80baf to get more accurate results

Additional details and impacted files

@@            Coverage Diff            @@
##            master      #171   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            1         1           
  Lines           81        81           
  Branches        17        17           
=========================================
  Hits            81        81           

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.