Skip to content

Update dependency zod to v4.1.11 #52

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

Merged
renovate merged 1 commit into from
Sep 20, 2025
Merged

Update dependency zod to v4.1.11 #52

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
8 changes: 4 additions & 4 deletions pr-review/package-lock.json
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion pr-review/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,7 +27,7 @@
"mollitia": "0.2.0",
"octokit": "5.0.3",
"parse-diff": "0.11.1",
"zod": "4.1.9"
"zod": "4.1.11"
Copy link

@github-actions github-actions bot Sep 20, 2025

Choose a reason for hiding this comment

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

Consider relaxing the exact version pin to allow minor and patch updates for zod. Using a caret (^) range ensures you pick up backwards-compatible improvements automatically:

"dependencies": {
  "zod": "^4.1.11"
}

This reduces the need for frequent manual bumps for every patch release and helps with keeping up-to-date with bug fixes.

},
"devDependencies": {
"@eslint/js": "9.36.0",
Comment on lines 27 to 33
Copy link

@github-actions github-actions bot Sep 20, 2025

Choose a reason for hiding this comment

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

The same set of dependencies appears in both pr-review/package.json and pr-summary/package.json. Maintaining them in two places can lead to drift and duplication.

• If this is a monorepo, consider moving shared dependencies into the root package.json and enabling workspaces.
• After migrating, remove the duplicate entries from each sub-package.
• Run npm install (or yarn install) at the root to regenerate the lockfile and ensure consistency across all packages.

Example root setup:

{
  "private": true,
  "workspaces": [
    "pr-review",
    "pr-summary"
  ],
  "dependencies": {
    "zod": "^4.1.11",
    "octokit": "^5.0.3",
    "parse-diff": "^0.11.1"
  }
}

Expand Down
8 changes: 4 additions & 4 deletions pr-summary/package-lock.json
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion pr-summary/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,7 @@
"mollitia": "0.2.0",
"octokit": "5.0.3",
"parse-diff": "0.11.1",
"zod": "4.1.9"
"zod": "4.1.11"
Copy link

@github-actions github-actions bot Sep 20, 2025

Choose a reason for hiding this comment

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

Consider relaxing the exact version pin to allow minor and patch updates for zod. Using a caret (^) range ensures you pick up backwards-compatible improvements automatically:

"dependencies": {
  "zod": "^4.1.11"
}

This reduces the need for frequent manual bumps for every patch release and helps with keeping up-to-date with bug fixes.

},
"devDependencies": {
"@eslint/js": "9.36.0",
Comment on lines 26 to 32
Copy link

@github-actions github-actions bot Sep 20, 2025

Choose a reason for hiding this comment

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

The same set of dependencies appears in both pr-review/package.json and pr-summary/package.json. Maintaining them in two places can lead to drift and duplication.

• If this is a monorepo, consider moving shared dependencies into the root package.json and enabling workspaces.
• After migrating, remove the duplicate entries from each sub-package.
• Run npm install (or yarn install) at the root to regenerate the lockfile and ensure consistency across all packages.

Example root setup:

{
  "private": true,
  "workspaces": [
    "pr-review",
    "pr-summary"
  ],
  "dependencies": {
    "zod": "^4.1.11",
    "octokit": "^5.0.3",
    "parse-diff": "^0.11.1"
  }
}

Expand Down