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 debug.
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.
With Integrationsfirst-class bot support landed on GitHub and we’ve rewritten Greenkeeper to take full advantage of it. Simpler setup, fewer pull-requests, faster than ever.
Screencast Try it today. Free for private repositories during beta.
Coverage remained the same at 97.126% when pulling 00ab348a8962753c8421cf2c0f9197ecfed1b909 on greenkeeper-debug-2.6.5 into 85ef1d0f9d20cedb524b3d7831e0f85fd536f82f on master.
Coverage remained the same at 97.126% when pulling 00ab348a8962753c8421cf2c0f9197ecfed1b909 on greenkeeper-debug-2.6.5 into 85ef1d0f9d20cedb524b3d7831e0f85fd536f82f on master.
Coverage remained the same at 97.126% when pulling 00ab348a8962753c8421cf2c0f9197ecfed1b909 on greenkeeper-debug-2.6.5 into 85ef1d0f9d20cedb524b3d7831e0f85fd536f82f on master.
Hello lovely humans,
debug just published its new version 2.6.5.
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 debug. 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 :sparkles:
You rock!
:palm_tree:
The new version differs by 8 commits .
14df14c
release 2.6.5
cae07b7
cleanup browser tests and fix null reference check on window.documentElement.style.WebkitAppearance (#447)
f311b10
release 2.6.4
1f01b70
Fix bug that would occure if process.env.DEBUG is a non-string value. (#444)
2f3ebf4
Update CHANGELOG.md
f5ae332
Update CHANGELOG.md
9742c5f
chore(): ignore bower.json in npm installations. (#437)
27d93a3
update "debug" to v0.7.3
See the full diff.
Screencast
Try it today. Free for private repositories during beta.