Skip to content

build: update find-cache-dir to version 3.1.0 #16128

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 1 commit into from
Nov 9, 2019

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 9, 2019

This PR contains the following updates:

Package Type Update Change
find-cache-dir dependencies minor 3.0.0 -> 3.1.0

Release Notes

avajs/find-cache-dir

v3.1.0

Compare Source

  • Return undefined if the found node_modules directory is not writable (#​19) 3cea1e7

Renovate configuration

📅 Schedule: "after 10pm every weekday,before 4am every weekday,every weekend" in timezone America/Tijuana.

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻️ Rebasing: Whenever PR becomes conflicted, or if you modify the PR title to begin with "rebase!".

🔕 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 Renovate Bot. View repository job log here.

@renovate renovate bot added the target: major This PR is targeted for the next major release label Nov 9, 2019
@mgechev mgechev merged commit f871228 into master Nov 9, 2019
@mgechev mgechev deleted the renovate/find-cache-dir-3.x branch November 9, 2019 19:50
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Dec 10, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
target: major This PR is targeted for the next major release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants