Adding support for jQuery 2.2.2. #203
Merged
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
|
@yoavaa, is there anything I can help you with in order to get the PR merged? |
|
@yoavaa ping? |
|
Wow, thanks! 💯 |
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.
I've just dumb-bumped the jquery dependency in the project, and the bundled "demo" jquery.js to the latest version, as there is a known security vulnerability in jquery 2.0.3 - jquery/jquery#2432.
Please review the pull request, and in case if the version bump of jquery - removing the known vulnerability from angular-tree-control - seems to make sense, consider merging it and creating a security maintenance release for angular-tree-control.
In case if there are any hidden dependencies/issues caused by this pull request, please let me know, and I'll fix them as soon as possible! :) I've checked the updated demo index.html, and it seems like, this change did not introduce any new issues (however there were issues around the "Events" part, but I decided, they are out of scope for this PR.)