Update marked to 0.7.0 #7326
Merged
Update marked to 0.7.0 #7326
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
jasongrout
added
the
tag:Backport
|
Thanks for making a pull request to JupyterLab! To try out this branch on binder, follow this link: |
|
@meeseeksdev backport to 1.x |
meeseeksmachine
pushed a commit
to meeseeksmachine/jupyterlab
that referenced
this pull request
Oct 11, 2019
jasongrout
added a commit
that referenced
this pull request
Oct 11, 2019
…6-on-1.x Backport PR #7326 on branch 1.x (Update marked to 0.7.0)
jasongrout
removed
the
tag:Backport
lock
bot
added
the
status:resolved-locked
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
References
Fixes #6479
Code changes
Upgrade marked.js to 0.7.0
User-facing changes
Some markdown bugs and security issues are fixed.
Backwards-incompatible changes
Based on #6479 (comment) and looking again at the marked.js 0.7.0 release notes, I think this is backwards compatible for our purposes. We're not using the options that make their release not backwards compatible, IIRC.