-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update mime to the latest version 🚀 #79
base: master
Are you sure you want to change the base?
Conversation
Version 1.3.6 just got published.Update to this version instead 🚀 CommitsThe new version differs by 8 commits0.
false See the full diff |
Version 1.4.0 just got published. |
Version 2.0.0 just got published.Update to this version instead 🚀 Release Notesv2.0.0
|
Version 2.0.2 just got published. |
Version 2.0.3 just got published. |
Version 2.0.5 just got published.Update to this version instead 🚀 CommitsThe new version differs by 15 commits ahead by 15, behind by 1.
See the full diff |
Version 2.1.0 just got published. |
Version 2.2.0 just got published. |
Version 2.2.1 just got published. |
Version 2.2.2 just got published.Update to this version instead 🚀 CommitsThe new version differs by 2 commits.
See the full diff |
Version 2.3.0 just got published. |
Version 2.3.1 just got published. |
Update to this version instead 🚀 CommitsThe new version differs by 7 commits.
See the full diff |
Update to this version instead 🚀 CommitsThe new version differs by 13 commits.
See the full diff |
|
|
|
|
🚨 Reminder! Less than one month left to migrate your repositories over to Snyk before Greenkeeper says goodbye on June 3rd! 💜 🚚💨 💚 Find out how to migrate to Snyk at greenkeeper.io
|
Version 1.3.5 of mime just got published.
The version 1.3.5 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 mime.
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.
Commits
The new version differs by 11 commits0.
902ec07
Use facets to prioritize when resolving type conflicts
19a4b97
Merge branch 'master' of github.com:broofa/node-mime
89d499e
Merge pull request #155 from WORMSS/patch-1
2f1f6a0
debug fix
76e8766
update types from latest version of mime-db
9515cda
Merge pull request #150 from taylorhutchison/master
691da1d
Removing duplicate scripts property.
a5c1455
Merge pull request #142 from billymoon/patch-1
9695770
Update package.json
6c3d324
Merge pull request #125 from pgilad/patch-1
d0715f3
update license attribute
false
See the full diff
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴