Update serve-favicon to version 2.4.1 🚀 #7
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,
serve-favicon just published its new version 2.4.1.
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 serve-favicon.
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!
🌴
GitHub Release
res._headers
private fieldIf-None-Match
has both*
and ETagsETag
matching to match specIf-None-Match
when noETag
headerDate.parse
instead ofnew Date
The new version differs by 50 commits .
dc00730
2.4.1
6963249
docs: remove Node.js 8 history note
bc7984e
lint: add newline to license file
c64330e
docs: update copyright year
644808e
docs: Gittip is now Gratipay
c425d06
docs: update install code block style
1665414
deps: [email protected]
271769c
build: [email protected]
9fcab00
build: test against Node.js 8.x nightly
80de876
Remove usage of res._headers private field
22be71f
build: [email protected]
48661c8
build: [email protected]
ff5c1a2
build: [email protected]
b2073b1
2.4.0
4d7024d
lint: use standard style in readme
There are 50 commits in total. See the full diff.
Screencast
Try it today. Free for private repositories during beta.