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 husky to v2 #272

Merged
merged 2 commits into from
May 11, 2019
Merged

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 5, 2019

This PR contains the following updates:

Package Type Update Change References
husky devDependencies major 1.3.1 -> 2.2.0 source

Release Notes

typicode/husky

v2.2.0

Compare Source

  • Improve Git worktree support

v2.1.0

Compare Source

  • Improve shell script portability by using . rather than source

v2.0.0

Compare Source

  • Update dependencies
  • Update messages
  • Breaking change drop Node 6 support

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 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 assigned surma May 5, 2019
@renovate renovate bot force-pushed the renovate/husky-2.x branch from 8de572e to 6a1a883 Compare May 9, 2019 15:53
@renovate renovate bot changed the title Update dependency husky to v2 chore(deps): update dependency husky to v2 May 11, 2019
@renovate renovate bot force-pushed the renovate/husky-2.x branch 3 times, most recently from d47fe5c to 2d8bca8 Compare May 11, 2019 18:02
@surma surma force-pushed the renovate/husky-2.x branch from 2d8bca8 to a2cbf71 Compare May 11, 2019 18:14
@googlebot
Copy link

So there's good news and bad news.

👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there.

😕 The bad news is that it appears that one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that here in the pull request.

Note to project maintainer: This is a terminal state, meaning the cla/google commit status will not change from this state. It's up to you to confirm consent of all the commit author(s), set the cla label to yes (if enabled on your project), and then merge this pull request when appropriate.

ℹ️ Googlers: Go here for more info.

@renovate
Copy link
Contributor Author

renovate bot commented May 11, 2019

PR has been edited

👷 This PR has received other commits, so Renovate will stop updating it to avoid conflicts or other problems. If you wish to abandon your changes and have Renovate start over you may click the "rebase" checkbox in the PR body/description.

@surma surma merged commit 504bbf8 into master May 11, 2019
@renovate renovate bot deleted the renovate/husky-2.x branch May 11, 2019 18:19
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