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.

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

Update dependency eslint-plugin-promise to v7 #62

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 24, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
eslint-plugin-promise ^6.1.1 -> ^7.0.0 age adoption passing confidence

Release Notes

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

v7.1.0

Compare Source

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.

Copy link
Contributor Author

renovate bot commented Jul 24, 2024

⚠️ Artifact update problem

Renovate failed to update artifacts 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: OPC_UA_Clients/Release2/IJT_Web_Client/package-lock.json
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.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   dev eslint-config-standard@"^17.0.0" 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     dev eslint-config-standard@"^17.0.0" 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-09-16T19_35_31_369Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-09-16T19_35_31_369Z-debug-0.log

File name: OPC_UA_Clients/Release1/NodeOPCUA_IJT_Client/package-lock.json
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.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   dev eslint-config-standard@"^17.0.0" 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     dev eslint-config-standard@"^17.0.0" 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-09-16T19_35_36_708Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-09-16T19_35_36_708Z-debug-0.log

@renovate renovate bot force-pushed the renovate/eslint-plugin-promise-7.x branch from be62cb2 to 8dbcfcb Compare August 28, 2024 12:52
@renovate renovate bot force-pushed the renovate/eslint-plugin-promise-7.x branch 3 times, most recently from c15a945 to 860966f Compare September 16, 2024 19:25
@mohitkumaragarwal mohitkumaragarwal changed the title Update dependency eslint-plugin-promise to v7 rebase!Update dependency eslint-plugin-promise to v7 Sep 16, 2024
@renovate renovate bot force-pushed the renovate/eslint-plugin-promise-7.x branch from 860966f to 89bd882 Compare September 16, 2024 19:35
@renovate renovate bot changed the title rebase!Update dependency eslint-plugin-promise to v7 Update dependency eslint-plugin-promise to v7 Sep 16, 2024
Copy link
Contributor Author

renovate bot commented Sep 16, 2024

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 7.x releases. But if you manually upgrade to 7.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

@renovate renovate bot deleted the renovate/eslint-plugin-promise-7.x branch September 16, 2024 20:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant