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 npm-check-updates to v11 #62

Merged
merged 1 commit into from
Jan 21, 2021

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 21, 2021

WhiteSource Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
npm-check-updates ^10.0.0 -> ^11.0.0 age adoption passing confidence

Release Notes

raineorshine/npm-check-updates

v11.0.0

Compare Source

Breaking
  • --packageFile - Now interprets its argument as a glob pattern. It is possible that a previously supplied argument may be interepreted differently now (though I'm not aware of specific instances). Due to our conservative release policy we are releasing as a major version upgrade and allowing developers to assess for themselves.
Features
  • --deep - Run recursively in current working directory. Alias of --packageFile '**/package.json'.

See: #​785


Renovate configuration

📅 Schedule: 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 WhiteSource Renovate. View repository job log here.

@amacar amacar merged commit 08f75ac into develop Jan 21, 2021
@amacar amacar deleted the renovate/npm-check-updates-11.x branch January 21, 2021 11:08
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.

2 participants