bump jsonpath-plus minimum version to 10.3.0

[kevinthenet]

Resolves vulnerability reported by Snyk.

For any new installations this should pick up 10.3.0, but this change ensures there's no risk of installing any problematic versions.

• npm test passes
• npm run generate yields no errors

[linux-foundation-easycla]

• ✅login: kevinthenet / (fd16760)

The committers listed above are authorized under a signed CLA.

[k8s-ci-robot]

Welcome @kevinthenet!

It looks like this is your first PR to kubernetes-client/javascript 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-client/javascript has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[brendandburns]

/lgtm
/approve

I wonder why @dependabot didn't send a PR for this.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: brendandburns, kevinthenet

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [brendandburns]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[kevinthenet]

@brendandburns

I wonder why @dependabot didn't send a PR for this.

I recall seeing a PR/commit of the sort before v1.x, but I think the file regressed or was undone by another PR. In any case, it would be nice if we could cherry-pick this commit to the 0.22.3 tag so folks that haven't upgraded to 1.x have the vulnerability saved as well, though I'm not sure if you're still supporting 0.22.x.

Happy to pitch in if needed.

[cjihrig]

It was bumped by dependabot in #2236.

[b96m]

would greatly appreciate a patch release for this on the 1.0.x track as soon as possible, multiple internal auditing tools have this as a critical severity

[b96m]

would greatly appreciate a patch release for this on the 1.0.x track as soon as possible, multiple internal auditing tools have this as a critical severity

bump on this, would really appreciate a patch, can help as needed @cjihrig @brendandburns

[cjihrig]

There is a v1.1.0 pending, although I don't know the exact timeline for a release.

[b96m]

There is a v1.1.0 pending, although I don't know the exact timeline for a release.

@cjihrig any way we can get a 1.0.1 or similar patch release for this? Security scanning tooling is freaking out about this issue

[cjihrig]

It looks like v1.1.0 was released a few days ago.

[b96m]

It looks like v1.1.0 was released a few days ago.

oh nice thanks for letting me know, I don't see a tag for it in GitHub but I do see the NPM release. Thanks