-
-
Notifications
You must be signed in to change notification settings - Fork 2
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 browserify to the latest version 🚀 #8
base: master
Are you sure you want to change the base?
Conversation
Version 15.1.0 just got published.Update to this version instead 🚀 Release Notesv15.1.0
CommitsThe new version differs by 8 commits.
See the full diff |
Version 15.2.0 just got published.Update to this version instead 🚀 CommitsThe new version differs by 9 commits.
See the full diff |
Version 16.0.0 just got published.Update to this version instead 🚀 CommitsThe new version differs by 10 commits.
See the full diff |
Version 16.1.1 just got published.Update to this version instead 🚀 CommitsThe new version differs by 9 commits.
See the full diff |
Version 16.2.0 just got published.Update to this version instead 🚀 Release Notesv16.2.0update the browser versions of
|
Version 16.2.1 just got published.Update to this version instead 🚀 Release Notesv16.2.1Fix relative Fix tests to work on Windows, and add Appveyor CI for Windows testing. CommitsThe new version differs by 8 commits.
See the full diff |
Version 16.2.2 just got published.Update to this version instead 🚀 Release Notesv16.2.2Remove some extraneous files from the published package. |
Update to this version instead 🚀 Release Notes for v16.2.3add empty stub for the change the "browser" field link to the browser-field-spec repo instead of the old gist. |
Update to this version instead 🚀 CommitsThe new version differs by 8 commits.
See the full diff |
|
|
|
Version 15.0.0 of browserify was just published.
The version 15.0.0 is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of browserify.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Commits
The new version differs by 22 commits.
d85aa76
Merge branch 'master' of github.com:browserify/browserify
0a0efe3
15.0.0
288675e
Changelog for 15.0.0
a9aaa99
Merge pull request #1793 from TehShrike/patch-3
89fab44
Set the node version in package.json
00c211d
Merge pull request #1785 from TehShrike/backticks-test
183162f
remove es6ify from yield test
3ccd552
Merge pull request #1743 from ryysud/add-nodejs-v8-to-travis
7c3e585
Bump module-deps dependency
5ec19ee
update git url, fixes #1786
13e9d80
add images to repo
2b5d187
Failing test for backtick quotes
9fad0c2
Merge pull request #1769 from browserify/pr-1218
e65a8d8
Remove v7 and add v9 to Travis CI
a1def79
Merge pull request #1770 from browserify/tap-10
There are 22 commits in total.
See the full diff
FAQ and help
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper bot 🌴