Update non-major dependencies #36
Conversation
|
This change updates both Walkthrough
Model: o4-mini | Prompt Tokens: 832 | Completion Tokens: 427 |
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
There was a problem hiding this comment.
Here’s a supportive AI-powered code review. Some suggestions explore possibilities rather than hard rules, so choose what aligns with your approach. You set the direction—AI is here to help along the way.
Model: o4-mini | Prompt Tokens: 1428 | Completion Tokens: 3137
| "octokit": "5.0.3", | ||
| "parse-diff": "0.11.1", | ||
| "zod": "4.0.14" | ||
| "zod": "4.0.16" |
There was a problem hiding this comment.
You’re currently pinning zod to an exact patch version. Pinning exact versions can lead to stale dependencies and missed patches. Consider using a caret range to automatically include future patch and minor fixes:
"zod": "^4.0.16"| "@eslint/js": "9.32.0", | ||
| "@types/node": "22.17.0", | ||
| "@eslint/js": "9.33.0", | ||
| "@types/node": "22.17.1", |
There was a problem hiding this comment.
Dev dependencies are also pinned to exact versions here. To streamline future maintenance and ensure you get backward-compatible updates, use caret ranges for these packages. For example:
"typescript": "^5.9.2",
"typescript-eslint": "^8.39.0",
"yaml": "^2.8.1"| "mollitia": "0.2.0", | ||
| "octokit": "5.0.3", | ||
| "parse-diff": "0.11.1", | ||
| "zod": "4.0.14" | ||
| "zod": "4.0.16" | ||
| }, | ||
| "devDependencies": { | ||
| "@eslint/js": "9.32.0", | ||
| "@types/node": "22.17.0", | ||
| "@eslint/js": "9.33.0", | ||
| "@types/node": "22.17.1", | ||
| "@vercel/ncc": "0.38.3", | ||
| "eslint": "9.32.0", | ||
| "eslint": "9.33.0", | ||
| "eslint-plugin-import": "2.32.0", | ||
| "eslint-plugin-sonarjs": "3.0.4", | ||
| "eslint-plugin-unicorn": "60.0.0", | ||
| "prettier": "3.6.2", | ||
| "tsx": "4.20.3", | ||
| "typescript": "5.8.3", | ||
| "typescript-eslint": "8.38.0", | ||
| "yaml": "2.8.0" | ||
| "typescript": "5.9.2", | ||
| "typescript-eslint": "8.39.0", | ||
| "yaml": "2.8.1" | ||
| } | ||
| } |
There was a problem hiding this comment.
I notice the same dependency bumps are applied in both pr-review and pr-summary package files. Maintaining duplicate version updates across multiple files is error-prone. Consider consolidating shared dependencies into a root package.json or adopting a monorepo solution (e.g., npm workspaces or Yarn workspaces) to keep versions in sync automatically.
| "octokit": "5.0.3", | ||
| "parse-diff": "0.11.1", | ||
| "zod": "4.0.14" | ||
| "zod": "4.0.16" |
There was a problem hiding this comment.
You’re pinning zod to an exact version here as well. Use a caret range to allow automatic patch and minor updates:
"zod": "^4.0.16"| "@eslint/js": "9.32.0", | ||
| "@types/node": "22.17.0", | ||
| "@eslint/js": "9.33.0", | ||
| "@types/node": "22.17.1", |
There was a problem hiding this comment.
Dev dependencies are locked to exact versions. Switching to caret ranges helps you receive non-breaking updates without manual bumps. For example:
"@eslint/js": "^9.33.0",
"@types/node": "^22.17.1",
"eslint": "^9.33.0",
"typescript": "^5.9.2"Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
This PR contains the following updates:
9.32.0->9.33.022.17.0->22.17.19.32.0->9.33.05.8.3->5.9.28.38.0->8.39.02.8.0->2.8.14.0.14->4.0.16Release Notes
eslint/eslint (@eslint/js)
v9.33.0Compare Source
eslint/eslint (eslint)
v9.33.0Compare Source
microsoft/TypeScript (typescript)
v5.9.2Compare Source
typescript-eslint/typescript-eslint (typescript-eslint)
v8.39.0Compare Source
🚀 Features
❤️ Thank You
You can read about our versioning strategy and releases on our website.
eemeli/yaml (yaml)
v2.8.1Compare Source
colinhacks/zod (zod)
v4.0.16Compare Source
v4.0.15Compare Source
Commits:
7e7e346Clean up docsf2949a8[docs] Fix migration guide upgrade command (#5021)d43cf19Fix recursive object initialization errors with check() and other methods (#5018)3de2b63fix: remove redundant Required<> from input and output type definitions (#5033)93553bdAdd needs info03cfa8d4.0.15Configuration
📅 Schedule: Branch creation - "every weekend" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.