Skip to content
This repository has been archived by the owner on Nov 7, 2020. It is now read-only.

chore(deps): update dependency codelyzer to v5.2.2 #307

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 19, 2019

This PR contains the following updates:

Package Type Update Change
codelyzer devDependencies minor 5.1.0 -> 5.2.2

Release Notes

mgechev/codelyzer

v5.2.2

Compare Source

v5.2.1

Compare Source

v5.2.0

Compare Source

Bug Fixes
Features
5.1.2 (2019-09-26)
Bug Fixes
5.1.1 (2019-09-19)
Bug Fixes

v5.1.2

Compare Source

v5.1.1

Compare Source


Renovate configuration

📅 Schedule: "after 10pm every weekday,every weekend,before 5am every weekday" (UTC).

🚦 Automerge: Enabled.

♻️ 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.

@renovate renovate bot force-pushed the renovate/codelyzer-5.x branch 2 times, most recently from f2c16af to 5cd3af5 Compare September 26, 2019 17:48
@renovate renovate bot changed the title chore(deps): update dependency codelyzer to v5.1.1 chore(deps): update dependency codelyzer to v5.1.2 Sep 26, 2019
@renovate renovate bot changed the title chore(deps): update dependency codelyzer to v5.1.2 chore(deps): update dependency codelyzer to v5.2.0 Oct 22, 2019
@renovate renovate bot changed the title chore(deps): update dependency codelyzer to v5.2.0 chore(deps): update dependency codelyzer to v5.2.1 Dec 22, 2019
@renovate renovate bot changed the title chore(deps): update dependency codelyzer to v5.2.1 chore(deps): update dependency codelyzer to v5.2.2 Apr 26, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant