-
Notifications
You must be signed in to change notification settings - Fork 31
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 🚀 #66
Open
greenkeeper
wants to merge
1
commit into
master
Choose a base branch
from
greenkeeper/browserify-16.2.2
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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 |
|
|
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Version 16.2.2 of browserify was just published.
The version 16.2.2 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.
Release Notes
v16.2.2Remove some extraneous files from the published package.
Commits
The new version differs by 175 commits.
fc30e50
16.2.2
36d7c9a
16.2.1
e34599a
Merge pull request #1819 from goto-bus-stop/appveyor
8e7cb87
Skip flaky test on Windows w old Node
3703154
Disable invalid json chars test in node 10
e39d609
Skip failing test on old Node on Windows
c428f0c
Fix external relative paths on Windows
c5120b7
Fix tests on Windows.
2d896a9
Try adding appveyor
00cc377
16.2.0
7005b6e
Merge pull request #1829 from browserify/deps
e333b14
Merge pull request #1827 from browserify/fix-cert
03ffac9
ci: Disable certificate check for very old npm
9345e21
Update string_decoder and vm builtin modules
25c71db
16.1.1
There are 175 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 🌴