Thanks to visit codestin.com
Credit goes to github.com

Skip to content

upgrading winston to ^3.11.0#120

Merged
jaredwray merged 1 commit intomainfrom
upgrading-winston-to-3.11.0
Jan 18, 2024
Merged

upgrading winston to ^3.11.0#120
jaredwray merged 1 commit intomainfrom
upgrading-winston-to-3.11.0

Conversation

@jaredwray
Copy link
Owner

@jaredwray jaredwray commented Jan 18, 2024

Please check if the PR fulfills these requirements

  • Followed the Contributing guidelines.
  • Tests for the changes have been added (for bug fixes/features) with 100% code coverage.
  • Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
upgrading winston to ^3.11.0

@codecov
Copy link

codecov bot commented Jan 18, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (743b437) 100.00% compared to head (b3b8333) 100.00%.

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #120   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           16        16           
  Lines          424       424           
  Branches        60        60           
=========================================
  Hits           424       424           

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

@jaredwray jaredwray merged commit 5a87068 into main Jan 18, 2024
@jaredwray jaredwray deleted the upgrading-winston-to-3.11.0 branch January 18, 2024 16:28
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.

1 participant

Comments