-
Notifications
You must be signed in to change notification settings - Fork 3
Update non-major dependencies #44
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.
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
Conversation
|
Both Walkthrough
Model: o4-mini | Prompt Tokens: 1034 | Completion Tokens: 478 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We’ve provided a code review with AI-powered guidance to help you spot improvements. Treat these ideas as optional suggestions rather than hard rules and choose what best suits your goals. You remain in charge—AI is here to assist your decision-making process.
Model: o4-mini | Prompt Tokens: 1678 | Completion Tokens: 3234
| "@sap-ai-sdk/ai-api": "1.17.0", | ||
| "@sap-ai-sdk/orchestration": "1.17.0", | ||
| "@sap-ai-sdk/ai-api": "1.18.0", | ||
| "@sap-ai-sdk/orchestration": "1.18.0", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Consider using semantic versioning ranges (e.g., ^1.18.0) instead of fixed versions to allow safe minor/patch upgrades without manual bumps. For example:
"@sap-ai-sdk/ai-api": "^1.18.0",
"@sap-ai-sdk/orchestration": "^1.18.0"| "@sap-ai-sdk/ai-api": "1.17.0", | ||
| "@sap-ai-sdk/orchestration": "1.17.0", | ||
| "@sap-ai-sdk/ai-api": "1.18.0", | ||
| "@sap-ai-sdk/orchestration": "1.18.0", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Similarly, swap fixed dependency versions for caret ranges to leverage semantic versioning and reduce future churn:
"@sap-ai-sdk/ai-api": "^1.18.0",
"@sap-ai-sdk/orchestration": "^1.18.0"| "@eslint/js": "9.34.0", | ||
| "@types/node": "22.17.2", | ||
| "@types/node": "22.18.0", | ||
| "@vercel/ncc": "0.38.3", | ||
| "eslint": "9.34.0", | ||
| "eslint-plugin-import": "2.32.0", | ||
| "eslint-plugin-sonarjs": "3.0.4", | ||
| "eslint-plugin-sonarjs": "3.0.5", | ||
| "eslint-plugin-unicorn": "60.0.0", | ||
| "prettier": "3.6.2", | ||
| "tsx": "4.20.5", | ||
| "typescript": "5.9.2", | ||
| "typescript-eslint": "8.40.0", | ||
| "typescript-eslint": "8.41.0", | ||
| "yaml": "2.8.1" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's a lot of duplicate devDependencies across pr-review and pr-summary. If you have a monorepo, consider hoisting these to the root package.json or using npm/yarn workspaces to avoid version drift and reduce maintenance. For example, in the root manifest:
{
"workspaces": ["packages/*"],
"devDependencies": {
"typescript": "^5.9.2",
"eslint": "^9.34.0",
"prettier": "^3.6.2",
"@types/node": "^22.18.0"
}
}| "@eslint/js": "9.34.0", | ||
| "@types/node": "22.17.2", | ||
| "@types/node": "22.18.0", | ||
| "@vercel/ncc": "0.38.3", | ||
| "eslint": "9.34.0", | ||
| "eslint-plugin-import": "2.32.0", | ||
| "eslint-plugin-sonarjs": "3.0.4", | ||
| "eslint-plugin-sonarjs": "3.0.5", | ||
| "eslint-plugin-unicorn": "60.0.0", | ||
| "prettier": "3.6.2", | ||
| "tsx": "4.20.5", | ||
| "typescript": "5.9.2", | ||
| "typescript-eslint": "8.40.0", | ||
| "typescript-eslint": "8.41.0", | ||
| "yaml": "2.8.1" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Apply the same monorepo/workspaces strategy here to manage shared devDependencies in one place and keep individual package manifests lean. This ensures consistency across modules.
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
This PR contains the following updates:
1.17.0->1.18.01.17.0->1.18.022.17.2->22.18.03.0.4->3.0.58.40.0->8.41.04.1.1->4.1.5Release Notes
SonarSource/SonarJS (eslint-plugin-sonarjs)
v3.0.5Compare Source
typescript-eslint/typescript-eslint (typescript-eslint)
v8.41.0Compare Source
This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
colinhacks/zod (zod)
v4.1.5Compare Source
Commits:
530415fUpdate docsb7b081dUpdate z.function() type to support array input (#5170)780cf574.1.5v4.1.4Compare Source
v4.1.3Compare Source
Commits:
98ff675Drop stringToBooleana410616Fix typo0cf4589fix(v4): toJSONSchema - add missing oneOf inside items in tuple conversion (#5146)8bf0c16fix(v4): toJSONSchema tuple path handling for draft-7 with metadata IDs (#5152)5c5fa90fix(v4): toJSONSchema - wrong record output when targetingopenapi-3.0(#5141)87b97ccdocs(codecs): update example to use payloadSchema (#5150)309f358fix(v4): toJSONSchema - output numbers with exclusive range correctly when targetingopenapi-3.0(#5139)1e71ca9docs: fix refine fn to encode works properly (#5148)a85ec3cfix(docs): correct example to useLooseDoginstead ofDog(#5136)3e982744.1.3v4.1.2Compare Source
Commits:
e45e61bImprove codec docs25a4c37fix(v4): toJSONSchema - wrong record tuple output when targetingopenapi-3.0(#5145)0fa4f46Use method form in codecs.mdx940383dUpdate JSON codec and docs3009fa84.1.2Configuration
📅 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.