Update winston to version 2.3.0 🚀 #26
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
evantahler
force-pushed
the
greenkeeper-winston-2.3.0
branch
from
88bed19 to
1fd4395
Compare
evantahler
force-pushed
the
greenkeeper-winston-2.3.0
branch
from
1fd4395 to
53af922
Compare
evantahler
force-pushed
the
greenkeeper-winston-2.3.0
branch
from
53af922 to
7505d17
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello lovely humans,
winston just published its new version 2.3.0.
This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of winston.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project ✨
You rock!
🌴
The new version differs by 185 commits .
739d802[dist] Version bump. 2.3.026664f4[dist] Modernize .travis.yml againd9050b8[dist] Add short message for 2.2.0 until a full CHANGELOG.md entry can be compiled.c98e6c5Merge pull request #839 from vanthome/patch-10198c17Merge pull request #852 from tamlyn/masterc351649Merge pull request #858 from tarrow/patch-155dac6dMerge pull request #859 from davidadas/masterab926c3Merge pull request #882 from khowen/update-docs1dedee5Merge pull request #894 from pkallos/master162c50fMerge pull request #898 from sinkingpoint/master391a956fix: use es5 only98fd982Update transports.jsddb8a2dUpdate transports.jsa8db2b3fix: remove expression dependencies07c70d1Update package.jsonThere are 185 commits in total. See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? ⚡
greenkeeper upgrade