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

chore(deps): replace dependency eslint-plugin-node with eslint-plugin-n ~14.0.0 #16

Closed
wants to merge 3 commits into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 2, 2024

Mend Renovate

This PR contains the following updates:

Package Type Update Change
eslint-plugin-node devDependencies replacement ~11.1 -> ~14.0.0

This is a special PR that replaces eslint-plugin-node with the community suggested minimal stable replacement version.


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.

Copy link
Contributor Author

renovate bot commented May 2, 2024

⚠ 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: ui/package-lock.json
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: @antora/ui-default@undefined
npm error Found: [email protected]
npm error node_modules/eslint
npm error   dev eslint@"~6.8" from the root project
npm error
npm error Could not resolve dependency:
npm error peer eslint@">=7.0.0" from [email protected]
npm error node_modules/eslint-plugin-n
npm error   dev eslint-plugin-n@"~14.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-05-06T09_18_39_016Z-eresolve-report.txt

npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-05-06T09_18_39_016Z-debug-0.log

@renovate renovate bot force-pushed the renovate/eslint-plugin-node-replacement branch 2 times, most recently from b808243 to 768fb36 Compare May 6, 2024 09:18
@renovate renovate bot force-pushed the renovate/eslint-plugin-node-replacement branch from 768fb36 to 11cc254 Compare June 3, 2024 15:09
Copy link
Contributor Author

renovate bot commented Jun 3, 2024

⚠️ 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: ui/package-lock.json
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: @antora/ui-default@undefined
npm error Found: [email protected]
npm error node_modules/eslint
npm error   dev eslint@"~6.8" from the root project
npm error
npm error Could not resolve dependency:
npm error peer eslint@">=7.0.0" from [email protected]
npm error node_modules/eslint-plugin-n
npm error   dev eslint-plugin-n@"~14.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-06-03T15_10_30_377Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-06-03T15_10_30_377Z-debug-0.log

@renovate renovate bot force-pushed the renovate/eslint-plugin-node-replacement branch from 11cc254 to 658cd5b Compare June 3, 2024 15:10
Copy link
Contributor Author

renovate bot commented Jun 3, 2024

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

@krisstern
Copy link
Member

The ui package is not ready for this change yet. See: https://gitlab.com/antora/antora-ui-default/-/blob/master/package.json

@krisstern krisstern closed this Oct 1, 2024
Copy link
Contributor Author

renovate bot commented Oct 1, 2024

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update (~14.0.0). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.

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-node-replacement branch October 1, 2024 10:07
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