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 devdependency chrome-launcher to v1 (2.x) #27218

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 14, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
chrome-launcher 0.15.2 -> 1.1.1 age adoption passing confidence

Release Notes

GoogleChrome/chrome-launcher (chrome-launcher)

v1.1.1

Compare Source

v1.1.0

Compare Source

v1.0.0

Compare Source

  • 37609a01 deps: upgrade lighthouse-logger to 2.0.1 (#​309)
  • dacd3578 Publish as ESM (#​302)
  • f9e43693 fix: always close file handles to stdout/stderr logs (#​259)

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - 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 Mend Renovate. View repository job log here.

Copy link

stackblitz bot commented May 14, 2024

Review PR in StackBlitz Codeflow Run & review this pull request in StackBlitz Codeflow.

@renovate renovate bot force-pushed the renovate/2.x-chrome-launcher-1.x branch 2 times, most recently from 29f891e to a5388f2 Compare May 19, 2024 17:47
@codecov-commenter
Copy link

codecov-commenter commented May 19, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 66.22%. Comparing base (06f9134) to head (1d4dda7).

Additional details and impacted files
@@           Coverage Diff           @@
##              2.x   #27218   +/-   ##
=======================================
  Coverage   66.22%   66.22%           
=======================================
  Files          93       93           
  Lines        4121     4121           
  Branches     1169     1169           
=======================================
  Hits         2729     2729           
  Misses       1126     1126           
  Partials      266      266           
Flag Coverage Δ
unittests 66.22% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@renovate renovate bot force-pushed the renovate/2.x-chrome-launcher-1.x branch 3 times, most recently from 5a16370 to 402a85f Compare May 25, 2024 06:58
Copy link

socket-security bot commented May 25, 2024

@renovate renovate bot force-pushed the renovate/2.x-chrome-launcher-1.x branch from 402a85f to 6c5d9dc Compare May 27, 2024 11:11
@renovate renovate bot force-pushed the renovate/2.x-chrome-launcher-1.x branch 2 times, most recently from 5904c58 to 6ca7353 Compare June 6, 2024 13:26
@renovate renovate bot force-pushed the renovate/2.x-chrome-launcher-1.x branch from 6ca7353 to 1d4dda7 Compare June 6, 2024 17:24
@danielroe danielroe closed this Jun 6, 2024
Copy link
Contributor Author

renovate bot commented Jun 6, 2024

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 1.x releases. But if you manually upgrade to 1.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

@renovate renovate bot deleted the renovate/2.x-chrome-launcher-1.x branch June 6, 2024 17:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants