bump dependency to address vulnerability in jsonpath-plus library

[massfords]

chore: bump version on jsonpath-plus
chore: bump version on asl-path-validator

[massfords]

@ChristopheBougere same problem with the commit lint rule

I definitely added a leading blank line in the commit message but perhaps my editor (WebStorm) removes the line. I don't see leading blank lines in my previous PR's commit messages.

Anyway, this is only 2 changes in package.json to address a vulnerability. Can you fix this PR or do a new one with the version changes?

FWIW, in a different project I have, I validate the commit message before the commit is done to ensure it's following conventional commit rules. Failing before the commit would be preferable to having it fail in CICD.

Thanks.

[ChristopheBougere]

Yeah that's curious...

Might be related to your editor.

Anyway I ammended your commit message and pushed it again, seems to work. I'll think about setting up git hooks for commitlint, that would make sense

Thanks for the fix

[ChristopheBougere]

Actually, husky is already setup on the repo. However, it only works if you run a npm install that will setup the hook (see the prepare script in package.json).

Maybe you have a working repo on a fork with everything installed, and this repo just tu push branches without npm installed?

[github-actions]

🎉 This PR is included in version 3.8.4 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀