Skip to content

📦 Update devDependencies (major) #194

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

Merged
merged 2 commits into from
May 21, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 8, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
eslint (source) 8.57.0 -> 9.3.0 age adoption passing confidence
eslint-plugin-sort-destructure-keys 1.6.0 -> 2.0.0 age adoption passing confidence
sinon (source) 17.0.2 -> 18.0.0 age adoption passing confidence
superagent 8.1.2 -> 9.0.2 age adoption passing confidence

Release Notes

eslint/eslint (eslint)

v9.3.0

Compare Source

v9.2.0

Compare Source

v9.1.1

Compare Source

v9.1.0

Compare Source

v9.0.0

Compare Source

mthadley/eslint-plugin-sort-destructure-keys (eslint-plugin-sort-destructure-keys)

v2.0.0

Compare Source

sinonjs/sinon (sinon)

v18.0.0

Compare Source

ladjs/superagent (superagent)

v9.0.2

Compare Source

  • Merge pull request #​1803 from alumni/fix-url-parse 329cc63
  • fix: replace deprecated url.parse() with new URL() 8ead63f
  • Merge pull request #​1804 from alumni/remove-semver 9406dae
  • chore: remove unnecessary semver checks 86c9bf4
  • Merge pull request #​1802 from alumni/fix-url-parse e996382
  • fix: replace deprecated node:url methods 7e20ced

v9.0.1

Compare Source

v9.0.0

Compare Source

  • fix: fixed ci job not installing npm deps 489708e
  • fix: fix numeric identifier issue ea2577e
  • fix: drop support for node < v14.18.0 due to formidable node:fs scope import statement (per #​1800) 23fe5ab
  • Merge pull request #​1800 from tomstrong64/master 03de30c
  • fix: formidable v3 multipart form contents mapped to expected format b9c7837
  • Update formidable 3ee138d
  • test: replace should with node:assert (#​1782) 1c8338b
  • test: replace should with node:assert (#​1780) 0dc80d1
  • Merge pull request #​1777 from jimmywarting/classify 83e92cb
  • classify agent fca95a3

Configuration

📅 Schedule: Branch creation - "after 12am every weekday" in timezone America/Los_Angeles, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR becomes conflicted, 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 Mend Renovate. View repository job log here.

Copy link
Contributor Author

renovate bot commented Apr 8, 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: package-lock.json
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @typescript-eslint/[email protected]
npm error Found: [email protected]
npm error node_modules/eslint
npm error   dev eslint@"9.2.0" from the root project
npm error   peer eslint@"^6.0.0 || ^7.0.0 || >=8.0.0" from @eslint-community/[email protected]
npm error   node_modules/@eslint-community/eslint-utils
npm error     @eslint-community/eslint-utils@"^4.4.0" from @typescript-eslint/[email protected]
npm error     node_modules/@typescript-eslint/utils
npm error       @typescript-eslint/utils@"7.8.0" from @typescript-eslint/[email protected]
npm error       node_modules/@typescript-eslint/eslint-plugin
npm error         dev @typescript-eslint/eslint-plugin@"7.8.0" from the root project
npm error       1 more (@typescript-eslint/type-utils)
npm error     @eslint-community/eslint-utils@"^4.2.0" from [email protected]
npm error   3 more (eslint-config-prettier, eslint-plugin-prettier, eslint-plugin-sort-destructure-keys)
npm error
npm error Could not resolve dependency:
npm error peer eslint@"^8.56.0" from @typescript-eslint/[email protected]
npm error node_modules/@typescript-eslint/eslint-plugin
npm error   dev @typescript-eslint/eslint-plugin@"7.8.0" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/eslint
npm error   peer eslint@"^8.56.0" from @typescript-eslint/[email protected]
npm error   node_modules/@typescript-eslint/eslint-plugin
npm error     dev @typescript-eslint/eslint-plugin@"7.8.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-06T15_52_22_074Z-eresolve-report.txt

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

@renovate renovate bot force-pushed the renovate/major-devdependencies branch 3 times, most recently from 2536627 to 030aa59 Compare April 15, 2024 18:30
@renovate renovate bot force-pushed the renovate/major-devdependencies branch 3 times, most recently from ee94f35 to cdc9d2d Compare April 23, 2024 19:52
@renovate renovate bot changed the title 📦 Update dependency eslint to v9 📦 Update devDependencies to v9 (major) Apr 23, 2024
@renovate renovate bot force-pushed the renovate/major-devdependencies branch from cdc9d2d to 3b0c87f Compare April 24, 2024 07:01
@renovate renovate bot changed the title 📦 Update devDependencies to v9 (major) 📦 Update devDependencies (major) Apr 24, 2024
@renovate renovate bot force-pushed the renovate/major-devdependencies branch 5 times, most recently from 88486d5 to a435684 Compare May 6, 2024 15:52
@renovate renovate bot force-pushed the renovate/major-devdependencies branch from a435684 to e51215d Compare May 10, 2024 16:42
Copy link
Contributor Author

renovate bot commented May 10, 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: package-lock.json
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @typescript-eslint/[email protected]
npm error Found: [email protected]
npm error node_modules/eslint
npm error   dev eslint@"9.3.0" from the root project
npm error   peer eslint@"^6.0.0 || ^7.0.0 || >=8.0.0" from @eslint-community/[email protected]
npm error   node_modules/@eslint-community/eslint-utils
npm error     @eslint-community/eslint-utils@"^4.4.0" from @typescript-eslint/[email protected]
npm error     node_modules/@typescript-eslint/utils
npm error       @typescript-eslint/utils@"7.10.0" from @typescript-eslint/[email protected]
npm error       node_modules/@typescript-eslint/eslint-plugin
npm error         dev @typescript-eslint/eslint-plugin@"7.10.0" from the root project
npm error       1 more (@typescript-eslint/type-utils)
npm error     @eslint-community/eslint-utils@"^4.2.0" from [email protected]
npm error   3 more (eslint-config-prettier, eslint-plugin-prettier, eslint-plugin-sort-destructure-keys)
npm error
npm error Could not resolve dependency:
npm error peer eslint@"^8.56.0" from @typescript-eslint/[email protected]
npm error node_modules/@typescript-eslint/eslint-plugin
npm error   dev @typescript-eslint/eslint-plugin@"7.10.0" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/eslint
npm error   peer eslint@"^8.56.0" from @typescript-eslint/[email protected]
npm error   node_modules/@typescript-eslint/eslint-plugin
npm error     dev @typescript-eslint/eslint-plugin@"7.10.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-20T18_13_25_347Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-05-20T18_13_25_347Z-debug-0.log

@renovate renovate bot force-pushed the renovate/major-devdependencies branch 3 times, most recently from 98bbacb to 2d2f89d Compare May 18, 2024 00:20
@renovate renovate bot force-pushed the renovate/major-devdependencies branch from 2d2f89d to 240e5f4 Compare May 20, 2024 18:13
Copy link
Contributor Author

renovate bot commented May 21, 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.

@danielrozenberg danielrozenberg force-pushed the renovate/major-devdependencies branch from 6b16328 to 1b761c0 Compare May 21, 2024 15:53
@danielrozenberg danielrozenberg merged commit 6f20f3d into main May 21, 2024
2 checks passed
@danielrozenberg danielrozenberg deleted the renovate/major-devdependencies branch May 21, 2024 15:55
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