Skip to content

chore(deps): Bump jsonpath from 1.1.1 to 1.2.1 #5

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
dependabot wants to merge 1 commit into
base: master
Choose a base branch
from
Open

chore(deps): Bump jsonpath from 1.1.1 to 1.2.1 #5

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion packages/frontend/editor-ui/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -78,7 +78,7 @@
"flatted": "catalog:",
"highlight.js": "catalog:frontend",
"humanize-duration": "^3.27.2",
"jsonpath": "^1.1.1",
"jsonpath": "^1.2.1",
Copy link

@appmod-pr-genie appmod-pr-genie bot Feb 12, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

JAS Confidence Score: 100%

JAS - Just a suggestion
Dependency Version Pinning

I noticed the jsonpath dependency is using a caret (^) version range. While the pnpm-lock.yaml file mitigates this for CI/CD, using ranged dependencies can sometimes lead to inconsistent builds across different environments if the lock file is ignored or regenerated. For maximum build reproducibility, let's consider pinning the dependency to an exact version.

Suggested change
"jsonpath": "^1.2.1",
"jsonpath": "1.2.1",

"lodash": "catalog:",
"luxon": "catalog:",
"n8n-workflow": "workspace:*",
Expand Down
Loading