coveralls
commented
7 years ago Coverage remained the same at 99.39% when pulling 5b95f56c6cca220349d0e456b33cf87c4d5d058c on greenkeeper-parse-link-header-1.0.0 into 65f6cfb368d24fd66e0f4283a72c30d797e28e8a on master.
Hello lovely humans,
parse-link-header just published its new version 1.0.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 parse-link-header. 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 3 commits .
e27d65c1.0.01ff32f7Fixes a problem with URLs containing a ';' character (Issue #14). Now properly pulls out the URL before the ending '>' before splitting on the ';' delimiter between the URL and the attributes.56f7f29Added format-link-header information to the README file.See the full diff.