Bump jsonpointer from 2.0.0 to 5.0.1

[dependabot]

Bumps jsonpointer from 2.0.0 to 5.0.1.

Release notes

Sourced from jsonpointer's releases.

Version 5.0.1

Changelog

• Fix incorrect typings for compile get/set methods (#58, thanks to @​haakemon)
• Fix null values throwing exception when traversing over while getting (#50, thanks to @​reckter)
• Fix tests for null and undefined assertions (janl/node-jsonpointer@a5706e8)

v5.0.0

5.0.0 (2021-10-31)

Bug Fixes

• Fix prototype pollution (#51)

  • The original, non-mutated objects are now returned if any of the keys __proto__, constructor or prototype are used in a json pointer.

  // returns the unmodified input {}
  jsonpointer.set({}, '/foo/__proto__/boo', 'polluted')

  • When passing non-string arrays to a .set operation, an error is thrown:

  // throws `new Error('Invalid JSON pointer. Must be of type string or number.')`
  jsonpointer.set({}, [['__proto__'], ['__proto__'], 'boo'], 'polluted')

v4.1.0

4.1.0 (2020-07-03)

Bug Fixes

• prototype pollution (234e343)

Features

• docs: thank contributors (b67e402)
• docs: use npm test (ad96a94)
• re-add semantic release (49b7074)

Version 4.0.1

Whitelist production relevant files in package.json. This decreases the npm package size a bit. janl/node-jsonpointer#26

Version 4.0.0

• null values now get set properly
• deleting a property is now supported by using jsonpointer.set(obj, '/val', undefined)

BREAKING CHANGES

... (truncated)

Commits

• 4a253c0 Adopt strictEqual changes and only return null when the get succeeded
• bad4983 Fix null values throwing exception when traversing over while getting
• a5706e8 test: Always use strictEqual to ensure null and undefined values are asserted...
• b8e1e6a fix incorrect typings for compile get/set methods
• c4de620 Merge pull request #53 from janl/release/5.0.0
• 8dbf304 feat: v5
• 84cf173 Merge pull request #52 from janl/fix/test
• f716e5c chore: more rip travis
• e2ae355 chore: remove comment
• d23693b chore: update primary branch
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.