Skip to content

chore(deps): update dependency eslint-plugin-promise to v7#32

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/eslint-plugin-promise-7.x
Open

chore(deps): update dependency eslint-plugin-promise to v7#32
renovate[bot] wants to merge 1 commit intomainfrom
renovate/eslint-plugin-promise-7.x

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate bot commented Dec 26, 2025 •
edited
Loading

This PR contains the following updates:

Package Change Age Confidence
eslint-plugin-promise ^6.6.0 → ^7.2.1 age confidence

Release Notes

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

v7.2.1

Compare Source

🩹 Fixes
  • no-callback-in-promise: false triggering of callback (#​574) (8324564)
🧹 Chores

v7.2.0

Compare Source

🌟 Features
🩹 Fixes
  • permit appropriate computed member expressions and prototype access (#​535) (4de9d43)
🧹 Chores

v7.1.0

Compare Source

🌟 Features
  • catch-or-return, prefer-await-to-then: do not report Cypress commands (#​495) (943f162)
  • prefer-await-to-then: ignore constructor scope unless with strict option (#​496) (7bffb7a)
  • new rule spec-only to check for non-spec Promise methods (#​502) (d6e9de1)
📚 Documentation
🧹 Chores

v7.0.0

Compare Source

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

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 was generated by Mend Renovate. View the repository job log.

@renovate
Copy link
Copy Markdown
Contributor Author

renovate bot commented Dec 26, 2025 •
edited
Loading

⚠️ 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: backend/package-lock.json
npm warn cli npm v11.11.1 does not support Node.js v18.20.8. This version of npm supports the following node versions: `^20.17.0 || >=22.9.0`. You can find the latest version at https://nodejs.org/.
npm warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm warn ERESOLVE overriding peer dependency
npm warn While resolving: [email protected]
npm warn Found: [email protected]
npm warn node_modules/eslint-plugin-promise
npm warn   dev eslint-plugin-promise@"^7.2.1" from the root project
npm warn
npm warn Could not resolve dependency:
npm warn peer eslint-plugin-promise@"^6.0.0" from [email protected]
npm warn node_modules/eslint-config-standard
npm warn   eslint-config-standard@"17.0.0" from [email protected]
npm warn   node_modules/eslint-config-standard-with-typescript
npm warn
npm warn Conflicting peer dependency: [email protected]
npm warn node_modules/eslint-plugin-promise
npm warn   peer eslint-plugin-promise@"^6.0.0" from [email protected]
npm warn   node_modules/eslint-config-standard
npm warn     eslint-config-standard@"17.0.0" from [email protected]
npm warn     node_modules/eslint-config-standard-with-typescript
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   dev eslint-plugin-promise@"^7.2.1" 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-with-typescript
npm error   dev eslint-config-standard-with-typescript@"^34.0.1" 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-with-typescript
npm error     dev eslint-config-standard-with-typescript@"^34.0.1" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-03-15T15_20_22_769Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-03-15T15_20_22_769Z-debug-0.log

@renovate renovate bot added the dependencies Pull requests that update a dependency file label Dec 26, 2025
@renovate renovate bot force-pushed the renovate/eslint-plugin-promise-7.x branch 2 times, most recently from 5e09d87 to c118a1d Compare December 27, 2025 18:19
@renovate renovate bot force-pushed the renovate/eslint-plugin-promise-7.x branch 3 times, most recently from 571c3b8 to 91a565e Compare February 9, 2026 08:07
@renovate renovate bot force-pushed the renovate/eslint-plugin-promise-7.x branch 2 times, most recently from e882501 to 31f323c Compare February 17, 2026 08:34
@renovate renovate bot force-pushed the renovate/eslint-plugin-promise-7.x branch from 31f323c to 8cb69c1 Compare February 21, 2026 17:06
@renovate renovate bot force-pushed the renovate/eslint-plugin-promise-7.x branch from 8cb69c1 to 4aa3312 Compare March 15, 2026 15:20
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

dependencies Pull requests that update a dependency file

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants