Skip to content
This repository was archived by the owner on Mar 11, 2026. It is now read-only.

fix(deps): roll back dependency @google-cloud/logging to ^3.0.2#224

Merged
JustinBeckwith merged 1 commit intomasterfrom
renovate/rollback-google-cloud-logging-3.x
Sep 18, 2018
Merged

fix(deps): roll back dependency @google-cloud/logging to ^3.0.2#224
JustinBeckwith merged 1 commit intomasterfrom
renovate/rollback-google-cloud-logging-3.x

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Sep 15, 2018

This Pull Request rolls back dependency @google-cloud/logging (source) from v^3.0.3 to v^3.0.2. This is necessary and important because v^3.0.3 cannot currently be found in the package's registry.

This PR has been generated by Renovate Bot.

@googlebot googlebot added the cla: yes This human has signed the Contributor License Agreement. label Sep 15, 2018
@renovate renovate Bot force-pushed the renovate/rollback-google-cloud-logging-3.x branch from cb5012e to 1e4b231 Compare September 17, 2018 17:41
@renovate renovate Bot force-pushed the renovate/rollback-google-cloud-logging-3.x branch from 1e4b231 to e57b064 Compare September 18, 2018 18:42
@codecov
Copy link
Copy Markdown

codecov Bot commented Sep 18, 2018

Codecov Report

Merging #224 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@          Coverage Diff          @@
##           master   #224   +/-   ##
=====================================
  Coverage     100%   100%           
=====================================
  Files           5      5           
  Lines         369    369           
=====================================
  Hits          369    369

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e206ea0...e57b064. Read the comment docs.

2 similar comments
@codecov
Copy link
Copy Markdown

codecov Bot commented Sep 18, 2018

Codecov Report

Merging #224 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@          Coverage Diff          @@
##           master   #224   +/-   ##
=====================================
  Coverage     100%   100%           
=====================================
  Files           5      5           
  Lines         369    369           
=====================================
  Hits          369    369

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e206ea0...e57b064. Read the comment docs.

@codecov
Copy link
Copy Markdown

codecov Bot commented Sep 18, 2018

Codecov Report

Merging #224 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@          Coverage Diff          @@
##           master   #224   +/-   ##
=====================================
  Coverage     100%   100%           
=====================================
  Files           5      5           
  Lines         369    369           
=====================================
  Hits          369    369

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e206ea0...e57b064. Read the comment docs.

@JustinBeckwith JustinBeckwith merged commit c452240 into master Sep 18, 2018
@renovate renovate Bot deleted the renovate/rollback-google-cloud-logging-3.x branch September 18, 2018 20:09
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Reviewers

1 more reviewer

@JustinBeckwith JustinBeckwith JustinBeckwith approved these changes

Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Labels

cla: yes This human has signed the Contributor License Agreement.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@JustinBeckwith @googlebot