chore(deps): update dependency json to v11#40
Open
renovate[bot] wants to merge 1 commit intomasterfrom
Open
Conversation
9d9497e to
537b2aa
Compare
This file contains hidden or 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
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.
This PR contains the following updates:
10.0.0->11.0.0Release Notes
trentm/json (json)
v11.0.0Compare Source
Backward incompatible and security-related change to parsing the
-d DELIMoption. (#148)The
-d DELIMoption allows specifying the field delimiter in output:The given "DELIM" string is parsed to allow escapes. For example:
Before this change, that parsing used
eval(), which allowed for unintendedcode execution if an untrusted argument to
-dwas provided. The fix forthis vulnerability changes to use
JSON.parse()to support escapes. Howeverthat results in a backward incompatible change, because the set of
JSON escapes is a subset of
JavaScript escapes.
The only escape I expect that would affect any current user would be the
null byte escape (
\0) which can be useful for processing values that mayhave spaces or other likely delimiter characters. For example:
BEFORE
AFTER
One must now use the JSON unicode escape syntax, '\u0000':
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.