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 dependency installed-check to v8 - autoclosed #1211

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Feb 27, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
installed-check ^3.0.0 -> ^8.0.0 age adoption passing confidence

Release Notes

voxpelli/node-installed-check (installed-check)

v8.0.1

Compare Source

v8.0.0

Compare Source

v7.1.2

Compare Source

  • Update installed-check-core 52d28d9

v7.1.1

Compare Source

  • Update installed-check-core b4dae70

v7.1.0

Compare Source

  • Feature/fix: Handle aliased packages #​42 b022cb0
  • Internal: Replace dependency-check with knip 5c69958

v7.0.0

Compare Source

  • BREAKING: Require Node 16 (else fails silently) f965611
  • Update dependencies 890e193

v6.0.5

Compare Source

  • Update dependencies

v6.0.4

Compare Source

v6.0.3

Compare Source

  • Fix regression on Windows 72fe7b4

v6.0.2

Compare Source

v6.0.1

Compare Source

v6.0.0

Compare Source

  • Breaking change: Now requires Node.js version matching ^14.18.0 || >=16.0.0, to match that of [email protected]`
  • Internal: Now an ESM based project

v5.0.0

Compare Source

  • Breaking change: Now requires Node.js version matching ^12.20.0 || ^14.13.1 || >=16.0.0, to match that of [email protected] which in turn sets it to ensure compatibility with ESM-based dependencies
  • Possibly breaking change: Uses new 5.x version of installed-check-core, which contains a newer engine intersection module as well as some alterations to errors, warnings and notices to make them more robust and consistent (thanks to eg. new tests)

v4.0.0

Compare Source

  • Breaking change: Now requires at least Node.js 12.x (somewhat following the LTS of Node.js itself)
  • Dependencies: Moved from 2.x to modern 4.x version of chalk
  • Dependencies: Now using meow instead of dashdash to parse the CLI input
  • Dependencies: Uses new 4.x version of installed-check-core, containing fewer dependencies that are more modern and eg. typed and async in themselves
  • Internal: Added strict type checking (using Typescript) verifying that the javascript code doesn't violate any assumptions.

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.

@CLAassistant
Copy link

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

@renovate renovate bot force-pushed the renovate/installed-check-8.x branch 2 times, most recently from 03ff819 to 6a75e92 Compare March 13, 2024 18:10
@renovate renovate bot force-pushed the renovate/installed-check-8.x branch from 6a75e92 to 73d9c98 Compare March 14, 2024 15:22
@voxpelli
Copy link

If you have questions or I can help merge this, then I'm happy to help

@renovate renovate bot changed the title chore(deps): update dependency installed-check to v8 chore(deps): update dependency installed-check to v8 - autoclosed Mar 23, 2024
@renovate renovate bot closed this Mar 23, 2024
@renovate renovate bot deleted the renovate/installed-check-8.x branch March 23, 2024 17:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants