codecharta icon indicating copy to clipboard operation
codecharta copied to clipboard

fix(deps): update npm dependencies not major update

Open renovate[bot] opened this issue 1 year ago • 1 comments

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
nw ^0.68.1 -> ^0.69.0 age adoption passing confidence
typescript (source) 4.5.5 -> 4.8.4 age adoption passing confidence
typescript-json-schema 0.53.0 -> 0.54.0 age adoption passing confidence

Release Notes

nwjs/npm-installer

v0.69.1

Compare Source

v0.69.0

Compare Source

Microsoft/TypeScript

v4.8.4

Compare Source

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

v4.8.3

Compare Source

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

v4.8.2

Compare Source

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

v4.7.4

Compare Source

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

v4.7.3

Compare Source

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

v4.7.2

Compare Source

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

v4.6.4

Compare Source

This release includes a bug fix for text formatting on certain ranges, which was impacting Visual Studio users.

For the complete list of fixed issues, check out the

Downloads are available on:

v4.6.3

Compare Source

This release includes fixes for

For the complete list of fixed issues, check out the

Downloads are available on:

v4.6.2

Compare Source

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

YousefED/typescript-json-schema

v0.54.0

Compare Source

v0.53.1

Compare Source


Configuration

📅 Schedule: Branch creation - "on the 2nd and 4th day instance on sunday after 9pm" in timezone Europe/Berlin, 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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • [ ] If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by Mend Renovate. View repository job log here.

renovate[bot] avatar Jul 24 '22 20:07 renovate[bot]

[CodeCharta Analysis] Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
No Duplication information No Duplication information

sonarcloud[bot] avatar Oct 21 '22 13:10 sonarcloud[bot]

⚠ 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: visualization/package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @angular/[email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/zone.js
npm ERR!   zone.js@"^0.12.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer zone.js@"~0.11.4" from @angular/[email protected]
npm ERR! node_modules/@angular/core
npm ERR!   @angular/core@"^12.2.12" from the root project
npm ERR!   peer @angular/core@"12.2.12" from @angular/[email protected]
npm ERR!   node_modules/@angular/animations
npm ERR!     @angular/animations@"^12.2.12" from the root project
npm ERR!     3 more (@angular/material, @angular/platform-browser, @testing-library/angular)
npm ERR!   10 more (@angular/cdk, @angular/common, @angular/forms, ...)
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/zone.js
npm ERR!   peer zone.js@"~0.11.4" from @angular/[email protected]
npm ERR!   node_modules/@angular/core
npm ERR!     @angular/core@"^12.2.12" from the root project
npm ERR!     peer @angular/core@"12.2.12" from @angular/[email protected]
npm ERR!     node_modules/@angular/animations
npm ERR!       @angular/animations@"^12.2.12" from the root project
npm ERR!       3 more (@angular/material, @angular/platform-browser, @testing-library/angular)
npm ERR!     10 more (@angular/cdk, @angular/common, @angular/forms, ...)
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/2022-11-23T15_23_45_080Z-eresolve-report.txt

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

renovate[bot] avatar Nov 07 '22 22:11 renovate[bot]

The changes to zone.js seem to have broken something. I've reverted them for now to be able to work on the TypeScript version bump better and will chack back tommorrow on that issue.

MW-Friedrich avatar Nov 23 '22 16:11 MW-Friedrich

Updating the linter to work with the new TS-Version was a success! Unfortunately we now have three new rules to worry about that bother the pipeline. They are:

  1. @typescript-eslint/prefer-optional-chain (error)
  2. @typescript-eslint/no-explicit-any (warning)
  3. unicorn/no-negated-condition (error)

The prefer-optional-chain is an easy fix in the code, but I am unsure about what to do about no-explicit-any and no-negated-condition. I would say we add no-negated-condition to the list of our ignored rules, but I am unsure what to do with no-explicit-any. @ce-bo Do you perhaps have some guidance for me?

MW-Friedrich avatar Nov 24 '22 12:11 MW-Friedrich

Since the update to TypeScript has been quite a big one, this PR also contains updates to:

  • @typescript-eslint/eslint-plugin
  • @typescript-eslint/parser
  • eslint
  • eslint-config-prettier
  • eslint-plugin-unicorn
  • ts-loader

Additionally, the new rules that came with the linter updates have been handled accordingly (fixing @typescript-eslint/prefer-optional-chain, disabling unicorn/no-negated-condition and keeping @typescript-eslint/no-explicit-any )

An update to zone.js is not jet possible due to ourAngular version, so it is omitted here.

MW-Friedrich avatar Nov 25 '22 09:11 MW-Friedrich

[CodeCharta Analysis] Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
No Duplication information No Duplication information

sonarcloud[bot] avatar Nov 25 '22 12:11 sonarcloud[bot]

[CodeCharta Visualization] Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

14.3% 14.3% Coverage
0.0% 0.0% Duplication

sonarcloud[bot] avatar Nov 25 '22 12:11 sonarcloud[bot]