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): ⬆️ update tooling (major) #22

Closed
wants to merge 1 commit into from

Conversation

peterjokumsen
Copy link
Member

@peterjokumsen peterjokumsen commented Sep 16, 2023

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@angular-eslint/eslint-plugin ~16.3.1 -> ~17.0.1 age adoption passing confidence
@angular-eslint/eslint-plugin-template ~16.3.1 -> ~17.0.1 age adoption passing confidence
@angular-eslint/template-parser ~16.3.1 -> ~17.0.1 age adoption passing confidence
eslint-plugin-unused-imports 2.0.0 -> 3.0.0 age adoption passing confidence

Release Notes

angular-eslint/angular-eslint (@​angular-eslint/eslint-plugin)

v17.0.1

Compare Source

Note: Version bump only for package @​angular-eslint/eslint-plugin

v17.0.0

Compare Source

Bug Fixes
  • no declarations for eslint plugins (2498238)

16.3.1 (2023-11-08)

Note: Version bump only for package @​angular-eslint/eslint-plugin

angular-eslint/angular-eslint (@​angular-eslint/eslint-plugin-template)

v17.0.1

Compare Source

Note: Version bump only for package @​angular-eslint/eslint-plugin-template

v17.0.0

Compare Source

Bug Fixes
  • no declarations for eslint plugins (2498238)
Features
  • eslint-plugin-template: [prefer-self-closing-tags] consider ng-content and ng-template elements (#​1573) (8e97d20)

16.3.1 (2023-11-08)

Note: Version bump only for package @​angular-eslint/eslint-plugin-template

angular-eslint/angular-eslint (@​angular-eslint/template-parser)

v17.0.1

Compare Source

Bug Fixes

v17.0.0

Compare Source

Note: Version bump only for package @​angular-eslint/template-parser

16.3.1 (2023-11-08)

Note: Version bump only for package @​angular-eslint/template-parser

sweepline/eslint-plugin-unused-imports (eslint-plugin-unused-imports)

v3.0.0

Compare Source


Configuration

📅 Schedule: Branch creation - "every weekend" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, 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 Renovate Bot.

@peterjokumsen
Copy link
Member Author

peterjokumsen commented Sep 16, 2023

⚠ 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: package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: @helderberg-pirates-baseball/[email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/zone.js
npm ERR!   zone.js@"^0.14.2" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer zone.js@"~0.13.0" from @angular/[email protected]
npm ERR! node_modules/@angular/core
npm ERR!   @angular/core@"16.2.12" from the root project
npm ERR!   peer @angular/core@"16.2.12" from @angular/[email protected]
npm ERR!   node_modules/@angular/animations
npm ERR!     @angular/animations@"16.2.12" 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/2023-11-11T16_19_52_349Z-eresolve-report.txt

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

File name: package.json
Command failed: npm ci --ignore-scripts
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: @helderberg-pirates-baseball/[email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/zone.js
npm ERR!   zone.js@"^0.14.2" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer zone.js@"~0.13.0" from @angular/[email protected]
npm ERR! node_modules/@angular/core
npm ERR!   @angular/core@"16.2.12" from the root project
npm ERR!   peer @angular/core@"16.2.12" from @angular/[email protected]
npm ERR!   node_modules/@angular/animations
npm ERR!     @angular/animations@"16.2.12" 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! /home/ubuntu/.npm/_logs/2023-11-11T16_19_54_247Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2023-11-11T16_19_54_247Z-debug-0.log

File name: package.json
Command failed: npm run prepare --if-present
sh: 1: husky: not found

File name: package.json
Command failed: npm ci --ignore-scripts
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: @helderberg-pirates-baseball/[email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/zone.js
npm ERR!   zone.js@"^0.14.2" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer zone.js@"~0.13.0" from @angular/[email protected]
npm ERR! node_modules/@angular/core
npm ERR!   @angular/core@"16.2.12" from the root project
npm ERR!   peer @angular/core@"16.2.12" from @angular/[email protected]
npm ERR!   node_modules/@angular/animations
npm ERR!     @angular/animations@"16.2.12" 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! /home/ubuntu/.npm/_logs/2023-11-11T16_19_56_291Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2023-11-11T16_19_56_291Z-debug-0.log

File name: package.json
Command failed: npm run prepare --if-present
sh: 1: husky: not found

File name: package.json
Command failed: npm ci --ignore-scripts
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: @helderberg-pirates-baseball/[email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/zone.js
npm ERR!   zone.js@"^0.14.2" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer zone.js@"~0.13.0" from @angular/[email protected]
npm ERR! node_modules/@angular/core
npm ERR!   @angular/core@"16.2.12" from the root project
npm ERR!   peer @angular/core@"16.2.12" from @angular/[email protected]
npm ERR!   node_modules/@angular/animations
npm ERR!     @angular/animations@"16.2.12" 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! /home/ubuntu/.npm/_logs/2023-11-11T16_19_58_180Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2023-11-11T16_19_58_180Z-debug-0.log

File name: package.json
Command failed: npm run prepare --if-present
sh: 1: husky: not found

File name: package.json
Command failed: npm ci --ignore-scripts
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: @helderberg-pirates-baseball/[email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/zone.js
npm ERR!   zone.js@"^0.14.2" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer zone.js@"~0.13.0" from @angular/[email protected]
npm ERR! node_modules/@angular/core
npm ERR!   @angular/core@"16.2.12" from the root project
npm ERR!   peer @angular/core@"16.2.12" from @angular/[email protected]
npm ERR!   node_modules/@angular/animations
npm ERR!     @angular/animations@"16.2.12" 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! /home/ubuntu/.npm/_logs/2023-11-11T16_20_00_186Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2023-11-11T16_20_00_186Z-debug-0.log

File name: package.json
Command failed: npm run prepare --if-present
sh: 1: husky: not found

@nx-cloud
Copy link

nx-cloud bot commented Sep 16, 2023

☁️ Nx Cloud Report

We didn't find any information for the current pull request with the commit 1389e7e.
Please verify you are running the latest version of the NxCloud runner.

Check the Nx Cloud Github Integration documentation for more information.

Alternatively, you can contact us at [email protected].


Sent with 💌 from NxCloud.

@peterjokumsen peterjokumsen force-pushed the renovate-github/major-tooling branch 11 times, most recently from 1643844 to e24da0a Compare September 23, 2023 05:15
@peterjokumsen peterjokumsen force-pushed the renovate-github/major-tooling branch 6 times, most recently from 0d2aa8b to 8e2f9fa Compare October 1, 2023 19:15
@peterjokumsen peterjokumsen force-pushed the renovate-github/major-tooling branch 5 times, most recently from 78537e8 to 5d77757 Compare October 14, 2023 02:22
@peterjokumsen peterjokumsen force-pushed the renovate-github/major-tooling branch 2 times, most recently from 0535b80 to d558422 Compare October 15, 2023 22:16
@peterjokumsen
Copy link
Member Author

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.

@peterjokumsen peterjokumsen force-pushed the renovate-github/major-tooling branch from d558422 to ad2d633 Compare October 21, 2023 02:22
@peterjokumsen peterjokumsen force-pushed the renovate-github/major-tooling branch 11 times, most recently from 655162c to 19f7520 Compare October 29, 2023 13:19
@peterjokumsen peterjokumsen force-pushed the renovate-github/major-tooling branch 5 times, most recently from eaed2be to fdce818 Compare November 7, 2023 20:19
@peterjokumsen peterjokumsen force-pushed the renovate-github/major-tooling branch from fdce818 to ef72dd9 Compare November 8, 2023 16:23
@peterjokumsen peterjokumsen changed the title chore(deps): ⬆️ update dependency eslint-plugin-unused-imports to v3 chore(deps): ⬆️ update tooling (major) Nov 8, 2023
@peterjokumsen peterjokumsen force-pushed the renovate-github/major-tooling branch 3 times, most recently from eba5d6a to f65b5c4 Compare November 9, 2023 21:15
auto-merge was automatically disabled November 9, 2023 21:16

Rebase merges are not allowed on this repository

@peterjokumsen peterjokumsen force-pushed the renovate-github/major-tooling branch 4 times, most recently from 2da0ec5 to da34b00 Compare November 11, 2023 14:14
@peterjokumsen peterjokumsen force-pushed the renovate-github/major-tooling branch from da34b00 to f116530 Compare November 11, 2023 16:20
@peterjokumsen peterjokumsen deleted the renovate-github/major-tooling branch November 11, 2023 20:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants