Skip to content

Update non-major dependencies - #120

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/non-major-dependencies
Open

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/non-major-dependencies

Conversation

@renovate

@renovate renovate Bot commented May 30, 2026

Copy link
Copy Markdown
Contributor

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence Type Update
@eslint/js (source) 9.39.49.39.5 age confidence devDependencies patch
@octokit/plugin-retry 8.1.08.1.1 age confidence dependencies patch
@octokit/plugin-throttling 11.0.311.0.5 age confidence dependencies patch
@sap-ai-sdk/ai-api (source) 2.10.02.16.0 age confidence dependencies minor
@sap-ai-sdk/orchestration (source) 2.10.02.16.0 age confidence dependencies minor
@types/node (source) 24.12.424.13.6 age confidence devDependencies minor
@vercel/ncc 0.38.40.45.0 age confidence devDependencies minor
actions/checkout v7.0.0v7.0.1 age confidence action patch
actions/setup-node v6.4.0v6.5.0 age confidence action minor
eslint (source) 9.39.49.39.5 age confidence devDependencies patch
eslint-plugin-sonarjs (source) 4.0.34.2.1 age confidence devDependencies minor
minimatch 10.2.510.2.6 age confidence dependencies patch
prettier (source) 3.8.33.9.8 age confidence devDependencies minor
tsx (source) 4.22.34.23.15 age confidence devDependencies minor
typescript-eslint (source) 8.59.48.70.0 age confidence devDependencies minor
yaml (source) 2.9.02.9.1 age confidence devDependencies patch
zod (source) 4.4.34.6.5 age confidence dependencies minor

Release Notes

eslint/eslint (@​eslint/js)

v9.39.5

Compare Source

Bug Fixes

Documentation

Chores

  • 458205f chore: update @eslint/eslintrc and @eslint/js for v9.39.5 (#​21077) (Francesco Trotta)
  • 202117b chore: package.json update for @​eslint/js release (Jenkins)
  • d9eb6ed test: disable warning for vm.constants.USE_MAIN_CONTEXT_DEFAULT_LOADER (#​21074) (Francesco Trotta)
  • 7b431a7 chore: override re2 dependency for @metascraper/helpers (#​21068) (Milos Djermanovic)
  • daf7791 chore: pin fflate@​0.8.2 (#​20895) (Milos Djermanovic)
  • daee8ba ci: use pnpm in eslint-flat-config-utils type integration test (#​20829) (Milos Djermanovic)
  • 116d4be ci: unpin Node.js 25.x in CI (#​20619) (Copilot)
octokit/plugin-retry.js (@​octokit/plugin-retry)

v8.1.1

Compare Source

Bug Fixes
octokit/plugin-throttling.js (@​octokit/plugin-throttling)

v11.0.5

Compare Source

Bug Fixes

v11.0.4

Compare Source

Bug Fixes
  • defer Bottleneck instantiation until first request (CF Workers compat) (#​850) (d711c52)
SAP/ai-sdk-js (@​sap-ai-sdk/ai-api)

v2.16.0

Compare Source

Patch Changes

v2.15.0

Compare Source

Patch Changes

v2.14.0

Compare Source

Patch Changes

v2.13.0

Compare Source

Patch Changes

v2.12.0

Compare Source

Patch Changes

v2.11.0

Compare Source

Patch Changes
SAP/ai-sdk-js (@​sap-ai-sdk/orchestration)

v2.16.0

Compare Source

Patch Changes

v2.15.0

Compare Source

Minor Changes
  • b61cb53: [compat] Deprecate OrchestrationConfigRef — use OrchestrationConfigRefById or OrchestrationConfigRefByName instead.
  • b61cb53: [feat] Split OrchestrationConfigRef into OrchestrationConfigRefById and OrchestrationConfigRefByName.
Patch Changes

v2.14.0

Compare Source

Minor Changes
  • b986b70: [feat] Add reasoning content support to the Orchestration client.
    reasoning_content fields were added on response, streaming delta, and assistant message types.
    The getReasoningContent() and getDeltaReasoningContent() convenience functions return the reasoning text from model responses.
  • b986b70: [feat] Added overrideConfig field to OrchestrationConfigRef to pass a PartialOrchestrationConfig that overrides parts of the stored orchestration configuration at request time.
    Streaming via .stream() now automatically sets stream.enabled = true in the partial configuration override, so clients using a stored orchestration configuration reference no longer require streaming to be pre-configured in the stored configuration.
  • cca7edd: [feat] Add GcpVertexAiEmbeddingModel type with gemini-embedding to @sap-ai-sdk/core.
    Add GcpVertexAiEmbeddingModel to the EmbeddingModel union in @sap-ai-sdk/orchestration.
Patch Changes

v2.13.0

Compare Source

Patch Changes

v2.12.0

Compare Source

Patch Changes

v2.11.0

Compare Source

Minor Changes
  • f72bb58: [feat] Update orchestration specification to v0.131.3
Patch Changes
vercel/ncc (@​vercel/ncc)

v0.45.0

Compare Source

Features

v0.44.1

Compare Source

Bug Fixes

v0.44.0

Compare Source

Features

v0.43.0

Compare Source

Changes
actions/checkout (actions/checkout)

v7.0.1

Compare Source

actions/setup-node (actions/setup-node)

v6.5.0

Compare Source

What's Changed

Full Changelog: actions/setup-node@v6.4.0...v6.5.0

SonarSource/SonarJS (eslint-plugin-sonarjs)

v4.2.1

Compare Source

v4.2.0

Compare Source

v4.1.0

Compare Source

isaacs/minimatch (minimatch)

v10.2.6

Compare Source

prettier/prettier (prettier)

v3.9.8

Compare Source

v3.9.7

Compare Source

  • Support Angular 22.2
  • Fix regressions in v3.9

🔗 Changelog

v3.9.6

Compare Source

v3.9.5

Compare Source

diff

Markdown: Cap ordered list mark at 999,999,999 (#​19351 by @​tats-u)

CommonMark parsers only support ordered list item numbers up to 999,999,999.

With this change, Prettier now caps the ordered list item number at 999,999,999 to ensure that the output is correctly parsed as an ordered list by CommonMark parsers. Numbers larger than 999,999,999 are not parsed as list item numbers and are left unchanged in the output:

<!-- Input -->
999999998. text
999999998. text
999999998. text
999999998. text

1234567890123456789012) text

<!-- Prettier 3.9.4 -->
999999998. text
999999999. text
1000000000. text
1000000001. text

1234567890123456789012) text

<!-- Prettier 3.9.5 -->
999999998. text
999999999. text
999999999. text
999999999. text

1234567890123456789012) text
Markdown: Avoid corrupting empty link with title (#​19487 by @​andersk)

Do not remove <> from an inline link or image with an empty URL and a title, as this removal would change its interpretation.

<!-- Input -->
[link](<> "title")

<!-- Prettier 3.9.4 -->
[link]( "title")

<!-- Prettier 3.9.5 -->
[link](<> "title")
Less: Remove extra spaces after [ in map lookups (#​19503 by @​kovsu)
// Input
.foo {
  color: #theme[ primary];
  color: #theme[@name];
  color: #theme[@@name];
}

// Prettier 3.9.4
.foo {
  color: #theme[ primary];
  color: #theme[ @name];
  color: #theme[ @@name];
}

// Prettier 3.9.5
.foo {
  color: #theme[primary];
  color: #theme[@name];
  color: #theme[@@name];
}
CSS: Prevent addition space in type() with + (#​19516 by @​bigandy)

This fixes the addition space before + in CSS type() declaration. For example type(<number>+) was being converted into type(<number> +) which is invalid CSS and does not work.

/* Input */
div {
  border-radius: attr(br type(<length>+));
}

/* Prettier 3.9.4 */
div {
  border-radius: attr(br type(<length> +));
}

/* Prettier 3.9.5 */
div {
  border-radius: attr(br type(<length>+));
}
Less: Remove spaces between merge markers and colons (#​19517 by @​kovsu)
// Input
a {
  box-shadow  +  : 0 0 1px #&#8203;000;
}

// Prettier 3.9.4
a {
  box-shadow+  : 0 0 1px #&#8203;000;
}

// Prettier 3.9.5
a {
  box-shadow+: 0 0 1px #&#8203;000;
}
Markdown: Preserve wiki links with aliases (#​19527 by @​kovsu)
<!-- Input -->
[[Foo:Bar]]

<!-- Prettier 3.9.4 -->
[[Foo]]

<!-- Prettier 3.9.5 -->
[[Foo:Bar]]
TypeScript: Fix comments being dropped on shorthand type import/export specifiers (#​19565 by @​kirkwaiblinger)
// Input
export { type /* comment */ T } from "foo";
import { type /* comment */ T } from "foo";

// Prettier 3.9.4
Error: Comment "comment" was not printed. Please report this error!

// Prettier 3.9.5
export { type /* comment */ T } from "foo";
import { type /* comment */ T } from "foo";
Miscellaneous: Preserving comments' placement property (#​19567 by @​Janther)

Prettier@​3.9.0 deleted an undocumented property on comments, which was already used by plugins, comment.placement is now available again after comment attach.

Flow: Stop enforcing empty module declaration to break (#​19568 by @​fisker)
// Input
declare module "foo" {}

// Prettier 3.9.4
declare module "foo" {
}

// Prettier 3.9.5
declare module "foo" {}
Angular: Support expression for exhaustive typechecking (#​19571 by @​fisker)
<!-- Input -->
@switch (state.mode) {
  @default never(state);
}

<!-- Prettier 3.9.4 -->
@switch (state.mode) {
  @default never;
}

<!-- Prettier 3.9.5 -->
@switch (state.mode) {
  @default never(state);
}
TypeScript: Ignore comments inside mapped type when checking type parameter comments (#​19572 by @​fisker)
// Input
foo<{
  // comment
  [key in keyof Foo]: number
}>();

// Prettier 3.9.4
foo<
  {
    // comment
    [key in keyof Foo]: number;
  }
>();

// Prettier 3.9.5
foo<{
  // comment
  [key in keyof Foo]: number;
}>();
Less: Fix adjacent block comments being corrupted (#​19574 by @​kovsu)
// Input
/* a *//* b */
/* a */* {
  color: red;
}

// Prettier 3.9.4
/* a */
/* b */
/* a * {
  color: red;
}

// Prettier 3.9.5
/* a */ /* b */
/* a */
* {
  color: red;
}
JavaScript: Handle dangling comments in SwitchStatement (#​19581 by @​fisker)
// Input
switch (foo) {
 // comment
}

// Prettier 3.9.4
switch (
  foo
  // comment
) {
}

// Prettier 3.9.5
switch (foo) {
  // comment
}
TypeScript: Remove space in comment-only object type (#​19583 by @​fisker)
// Input
var foo = {
  /* comment */
};
type Foo = {
  /* comment */
};

// Prettier 3.9.4
var foo = {/* comment */};
type Foo = { /* comment */ };

// Prettier 3.9.5
var foo = {/* comment */};
type Foo = {/* comment */};

v3.9.4

Compare Source

v3.9.3

Compare Source

v3.9.2

Compare Source

v3.9.1

Compare Source

v3.9.0

Compare Source

diff

🔗 Release Notes

v3.8.5

Compare Source

v3.8.4

Compare Source

diff

Markdown: Fix blank lines between list items and nested sub-lists being removed in Markdown/MDX (#​17746 by @​byplayer)

Prettier was removing blank lines between list items and their nested sub-lists, converting loose lists into tight lists and changing their semantic meaning.

<!-- Input -->
- a

  - b

- c

  - d

<!-- Prettier 3.8.3 -->
- a
  - b
- c
  - d

<!-- Prettier 3.8.4 -->
- a

  - b

- c

  - d
privatenumber/tsx (tsx)

v4.23.15

Compare Source

Bug Fixes
  • exclude bare builtins from namespace inheritance (38e1588)
  • expose require.cache and require.extensions to tsImport CommonJS modules (2da3407)
  • make namespaced register() overloads portable for declaration emit (562c434)

This release is also available on:

v4.23.14

Compare Source

v4.23.13

Compare Source

v4.23.12

Compare Source

Bug Fixes

This release is also available on:

v4.23.11

Compare Source

v4.23.10

Compare Source

Bug Fixes

This release is also available on:

v4.23.9

Compare Source

Bug Fixes
  • map Node test locations (2f55884)
  • support data URLs in tsImport (b94f46f)

This release is also available on:

v4.23.8

Compare Source

Bug Fixes
  • preserve package subpath resolution (be1315e)
  • preserve typeless ESM dependency exports (70dfc5e)

This release is also available on:

v4.23.7

Compare Source

Bug Fixes
  • prevent tsImport cache collisions (4e5a138)

This release is also available on:

v4.23.6

Compare Source

v4.23.5

Compare Source

v4.23.4

Compare Source

Bug Fixes
  • cli: allow async process.once() signal handlers to finish (#​827) (2afc7bb)

This release is also available on:

v4.23.3

Compare Source

Bug Fixes

This release is also available on:

v4.23.2

Compare Source

v4.23.1

Compare Source

Bug Fixes
  • support tsImport after global preload (8d4ffc2)
  • watch: avoid clearing piped output (95d0672)
  • watch: treat script and dependency paths literally (79fddde)
Performance Improvements
  • index transform cache lazily (e818ad6)
  • load esbuild lazily in CLI (d067938)
  • map Node TypeScript formats directly (cdcc623)
  • use sync module hooks on Node v22.22.3+ (f8992f1)

This release is also available on:

v4.23.0

Compare Source

Bug Fixes
Features

This release is also available on:

v4.22.5

Compare Source

Bug Fixes
  • isolate hook state per async module.register() registration (a305f36)

This release is also available on:

v4.22.4

Compare Source

Bug Fixes
  • resolve CommonJS directory requires inside dependencies (#​803) (1ce8463)

This release is also available on:

typescript-eslint/typescript-eslint (typescript-eslint)

v8.70.0

Compare Source

🩹 Fixes
  • eslint-plugin: [no-deprecated] report deprecated imported values used in object shorthand properties (#​12780)
❤️ Thank You

See GitHub Releases for more information.

You can read about our versioning strategy and releases on our website.

v8.69.0

Compare Source

This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.

See GitHub Releases for more information.

You can read about our versioning strategy and releases on our website.

v8.68.0

Compare Source

This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.

See GitHub Releases for more information.

You can read about our versioning strategy and releases on our website.

v8.67.0

Compare Source

🚀 Features
  • typescript-eslint: export basic globs for using tseslint (#​12105)
❤️ Thank You

See GitHub Releases for more information.

You can read about our versioning strategy and releases on our website.

v8.66.0

Compare Source

This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.

See GitHub Releases for more information.

You can read about our versioning strategy and releases on our website.

v8.65.0

Compare Source

🚀 Features
  • add warning when TS 7 is detected (#​12529)
❤️ Thank You

See GitHub Releases for more information.

You can read about our versioning strategy and releases on our website.

v8.64.0

Compare Source

8.64.0 (2026-07-13)

🚀 Features
  • support parsing import defer (#​12513)
  • eslint-plugin: [no-loop-func] support using / await using declarations and deprecate the rule (#​12500)
  • typescript-estree: throw for invalid definite assignment in class properties (#​12543)
🩹 Fixes
  • eslint-plugin: [require-array-sort-compare] handle constrained arrays (#​12512)
❤️ Thank You

See GitHub Releases for more information.

You can read about our versioning strategy and releases on our website.

v8.63.0

Compare Source

This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.

See GitHub Releases for more information.

You can read about our versioning strategy and releases on our website.

v8.62.1

Compare Source

This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.

See GitHub Releases for more information.

You can read about our versioning strategy and releases on our website.

v8.62.0

Compare Source

🚀 Features
  • remove redundant package.json "files" (#​12444)
❤️ Thank You

See GitHub Releases for more information.

You can read about our versioning strategy and [releases](https://typescr

Important

✂ PR body was truncated to here.


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • "every weekend"
  • 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.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot added the renovate label May 30, 2026
@renovate
renovate Bot enabled auto-merge (squash) May 30, 2026 01:06
@github-actions

Copy link
Copy Markdown

Updated the AI SDK and linting tooling to their latest minor releases across both the PR review and summary services for consistency and to incorporate recent fixes and improvements.

Walkthrough

  • Chore: Bumped @sap-ai-sdk/ai-api and @sap-ai-sdk/orchestration from v2.10.0 to v2.11.0 in both pr-review and pr-summary, ensuring access to the latest enhancements.
  • Chore: Upgraded typescript-eslint from v8.59.4 to v8.60.0, bringing in updated linting rules and bug fixes.

Model: o4-mini-2025-04-16 | Prompt Tokens: 672 | Completion Tokens: 404

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Enjoy this friendly AI-assisted code review. Some suggestions come from predictions and may not always be perfect. Feel free to choose the ideas that fit your style. Your choices guide the process, and AI is here to help.
Model: o4-mini-2025-04-16 | Prompt Tokens: 1204 | Completion Tokens: 1921

Comment thread pr-review/package.json Outdated
Comment on lines +23 to +24
"@sap-ai-sdk/ai-api": "2.10.0",
"@sap-ai-sdk/orchestration": "2.10.0",
"@sap-ai-sdk/ai-api": "2.11.0",
"@sap-ai-sdk/orchestration": "2.11.0",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Consider using a caret (^) range for SDK dependencies so you automatically receive compatible patch updates without manually bumping each time. For example:

"@sap-ai-sdk/ai-api": "^2.11.0",
"@sap-ai-sdk/orchestration": "^2.11.0",

Comment thread pr-review/package.json Outdated
Comment on lines +23 to +24
"@sap-ai-sdk/ai-api": "2.10.0",
"@sap-ai-sdk/orchestration": "2.10.0",
"@sap-ai-sdk/ai-api": "2.11.0",
"@sap-ai-sdk/orchestration": "2.11.0",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Before upgrading to 2.11.0, verify the upstream changelog for any breaking changes or required migration steps. You could add a comment or link to the changelog in your release notes:

# Upgrade @sap-ai-sdk to 2.11.0
- See https://github.com/SAP/ai-sdk/releases/tag/v2.11.0 for breaking changes

Comment thread pr-review/package.json Outdated
"tsx": "4.22.3",
"typescript": "6.0.3",
"typescript-eslint": "8.59.4",
"typescript-eslint": "8.60.0",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Similar to the SDK bump, consider using a caret range for the ESLint plugin dependency to get minor fixes automatically:

"typescript-eslint": "^8.60.0",

Comment thread pr-summary/package.json Outdated
Comment on lines +22 to +23
"@sap-ai-sdk/ai-api": "2.10.0",
"@sap-ai-sdk/orchestration": "2.10.0",
"@sap-ai-sdk/ai-api": "2.11.0",
"@sap-ai-sdk/orchestration": "2.11.0",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

This workspace also upgrades the SAP AI SDK. To keep versioning consistent across workspaces and simplify future bumps, you might extract these shared dependencies into the root package.json or a shared configs file.

Comment thread pr-summary/package.json Outdated
"tsx": "4.22.3",
"typescript": "6.0.3",
"typescript-eslint": "8.59.4",
"typescript-eslint": "8.60.0",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Ensure that bumping typescript-eslint here aligns with your overall ESLint config. If you have a centralized ESLint setup, consider updating it in one place instead of per-package.

@renovate
renovate Bot force-pushed the renovate/non-major-dependencies branch from a9b07a7 to ab6d417 Compare May 31, 2026 14:26
@github-actions

Copy link
Copy Markdown

This update standardizes dependency versions across both the pr-review and pr-summary packages, ensuring that core AI SDK modules, tooling runtimes, and linting plugins are aligned to their latest patch releases for improved stability and compatibility.

Walkthrough

  • Chore: Updated SAP AI SDK modules (@sap-ai-sdk/ai-api and @sap-ai-sdk/orchestration) to v2.11.0 across pr-review and pr-summary for minor enhancements and compatibility improvements.
  • Chore: Upgraded TSX runtime from 4.22.3 to 4.22.4 to incorporate recent stability and performance fixes in both packages.
  • Chore: Bumped typescript-eslint plugin to 8.60.0 to ensure up-to-date linting rules and code quality consistency.

Model: o4-mini-2025-04-16 | Prompt Tokens: 756 | Completion Tokens: 949 | Diff Range: a9b07a7...ab6d417

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

We’ve assembled a friendly, AI-powered review of your code with practical suggestions. Treat each point as a flexible idea rather than a strict rule. Choose what aligns with your goals and style. You’re in control of the final decisions, and AI is here to support you every step of the way.
Model: o4-mini-2025-04-16 | Prompt Tokens: 924 | Completion Tokens: 2148 | Diff Range: a9b07a7...ab6d417

Comment thread pr-review/package.json Outdated
"eslint-plugin-unicorn": "64.0.0",
"prettier": "3.8.3",
"tsx": "4.22.3",
"tsx": "4.22.4",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

It looks like you’re bumping the tsx version explicitly rather than using a semver range. For better flexibility and to automatically pick up compatible patch/minor updates, consider using a caret prefix. This way you’ll avoid manual bumps for every small release.

-    "tsx": "4.22.4",
+    "tsx": "^4.22.4",

Comment thread pr-summary/package.json Outdated
Comment on lines 37 to 43
"eslint-plugin-sonarjs": "4.0.3",
"eslint-plugin-unicorn": "64.0.0",
"prettier": "3.8.3",
"tsx": "4.22.3",
"tsx": "4.22.4",
"typescript": "6.0.3",
"typescript-eslint": "8.59.4",
"typescript-eslint": "8.60.0",
"yaml": "2.9.0"

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

I see the same set of ESLint and Prettier dependencies repeated in both pr-review and pr-summary packages. You could centralize shared devDependencies in a workspace root to avoid duplication and ensure consistency across all sub-packages.

For example, in your monorepo root package.json:

{
  "name": "my-monorepo",
  "private": true,
  "workspaces": [
    "pr-review",
    "pr-summary"
  ],
  "devDependencies": {
    "eslint-plugin-sonarjs": "^4.0.3",
    "eslint-plugin-unicorn": "^64.0.0",
    "prettier": "^3.8.3",
    "tsx": "^4.22.4",
    "typescript": "^6.0.3",
    "@typescript-eslint/eslint-plugin": "^8.60.0",
    "yaml": "^2.9.0"
  }
}

Then remove these entries from each sub-package’s devDependencies. This reduces maintenance overhead and keeps versions in sync.

@renovate
renovate Bot force-pushed the renovate/non-major-dependencies branch from ab6d417 to 11f7224 Compare June 8, 2026 03:57
@github-actions

github-actions Bot commented Jun 8, 2026

Copy link
Copy Markdown

This update refreshes CI workflows by upgrading the actions/checkout step and synchronizes package dependencies for pr-summary and pr-review modules. All internal SDKs, HTTP clients, and dev toolchains receive minor version bumps to align with the latest releases. This ensures more stable builds and up-to-date linting, without changing external behavior.

Walkthrough

  • Chore: Upgrades GitHub Actions checkout to v6.0.3, improving overall CI stability.
  • Chore: Bumps internal @sap-ai-sdk packages and axios to latest minor releases for bugfixes and enhancements.
  • Chore: Updates development tooling (TypeScript, Node types, ESLint, tsx) to keep linting and builds current.

Model: o4-mini-2025-04-16 | Prompt Tokens: 1883 | Completion Tokens: 1258 | Diff Range: ab6d417...11f7224

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Thank you for sharing your code. I’ve added AI-powered suggestions to help you refine your work. These are ideas, not hard rules—feel free to pick what suits you. Your expertise and choices drive the final outcome. Let me know if you’d like more feedback or support.
Model: o4-mini-2025-04-16 | Prompt Tokens: 2764 | Completion Tokens: 2959 | Diff Range: ab6d417...11f7224

Comment thread .github/workflows/build.yaml Outdated
Comment on lines 23 to 26
uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
uses: actions/checkout@df4cb1c069e1874edd31b4311f1884172cec0e10 # v6.0.3
with:
ref: ${{ env.SOURCE_BRANCH }}
path: source-folder

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

The actions/checkout step is pinned to a specific commit SHA multiple times, making maintenance harder when bumping versions. You can use the version tag (e.g., v6) and DRY out the repeated checkout configuration by leveraging YAML anchors or environment variables. For example:

env:
  CHECKOUT_VERSION: v6

jobs:
  prepare:
    steps:
      - name: Checkout source branch
        &checkout-source
        uses: actions/checkout@${{ env.CHECKOUT_VERSION }}
        with:
          ref: ${{ env.SOURCE_BRANCH }}
          path: source-folder

      - name: Checkout release branch
        <<: *checkout-source
        with:
          ref: ${{ env.RELEASE_BRANCH }}
          path: release-folder

Comment thread .github/workflows/code-quality.yaml Outdated
Comment on lines 23 to 26
uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
uses: actions/checkout@df4cb1c069e1874edd31b4311f1884172cec0e10 # v6.0.3
- name: Setup Node
uses: actions/setup-node@48b55a011bda9f5d6aeb4c2d9c7362e8dae4041e # v6.4.0
with:

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Similar to the build workflow, the checkout step is repeated and pinned to a commit SHA. You can improve readability and reduce duplication by using the tag actions/checkout@v6 and introducing a YAML anchor or an environment variable:

env:
  CHECKOUT_ACTION: v6

jobs:
  lint:
    steps:
      - name: Checkout source branch
        &checkout-step
        uses: actions/checkout@${{ env.CHECKOUT_ACTION }}
        with:
          path: [pr-summary, pr-review]

      # Reuse for another job
      - name: Checkout source branch again
        <<: *checkout-step

Comment thread pr-review/package.json Outdated
Comment on lines +23 to +25
"@sap-ai-sdk/ai-api": "2.10.0",
"@sap-ai-sdk/orchestration": "2.10.0",
"axios": "1.16.1",
"@sap-ai-sdk/ai-api": "2.11.0",
"@sap-ai-sdk/orchestration": "2.11.0",
"axios": "1.17.0",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Pinning dependencies to exact versions prevents receiving patch updates automatically. Consider using caret ranges (^) to allow non-breaking updates:

- "@sap-ai-sdk/ai-api": "2.11.0",
- "@sap-ai-sdk/orchestration": "2.11.0",
- "axios": "1.17.0",
+ "@sap-ai-sdk/ai-api": "^2.11.0",
+ "@sap-ai-sdk/orchestration": "^2.11.0",
+ "axios": "^1.17.0",

Comment thread pr-review/package.json Outdated
Comment on lines +33 to +34
"@eslint/js": "9.39.4",
"@types/node": "24.12.4",
"@types/node": "24.13.1",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Dependencies in devDependencies are not sorted alphabetically, which can make diffs noisy. Also apply caret ranges for consistency:

- "@types/node": "24.13.1",
+ "@types/node": "^24.13.1",

Comment thread pr-summary/package.json Outdated
Comment on lines +22 to +24
"@sap-ai-sdk/ai-api": "2.10.0",
"@sap-ai-sdk/orchestration": "2.10.0",
"axios": "1.16.1",
"@sap-ai-sdk/ai-api": "2.11.0",
"@sap-ai-sdk/orchestration": "2.11.0",
"axios": "1.17.0",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

As with the review workflow, use caret ranges for your production dependencies to allow automatic patch and minor upgrades:

- "@sap-ai-sdk/ai-api": "2.11.0",
- "@sap-ai-sdk/orchestration": "2.11.0",
- "axios": "1.17.0",
+ "@sap-ai-sdk/ai-api": "^2.11.0",
+ "@sap-ai-sdk/orchestration": "^2.11.0",
+ "axios": "^1.17.0",

Comment thread pr-summary/package.json Outdated
"devDependencies": {
"@eslint/js": "9.39.4",
"@types/node": "24.12.4",
"@types/node": "24.13.1",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Sorting devDependencies alphabetically and using caret ranges will keep your manifest tidy and ensure minor/patch updates:

- "@types/node": "24.13.1",
+ "@types/node": "^24.13.1",

@renovate
renovate Bot force-pushed the renovate/non-major-dependencies branch from 11f7224 to fda456f Compare June 8, 2026 20:04
@github-actions

github-actions Bot commented Jun 8, 2026

Copy link
Copy Markdown

Updated the GitHub workflows to use the latest checkout action and bumped several package versions in the PR summary and review modules. These changes keep CI processes aligned with the most recent enhancements and ensure that internal SDKs and tooling dependencies are up-to-date for improved stability and security.

Walkthrough

  • Chore: Upgraded actions/checkout to v6.0.3 across build and code-quality workflows for consistency and the latest security patches.
  • Chore: Updated internal dependencies in both pr-summary and pr-review packages (SAP AI SDKs, axios, Node types, TSX, ESLint plugins, TypeScript ESLint) to their newest minor releases.
  • Chore: No user-facing functionality changed; these are under-the-hood maintenance updates.

Model: o4-mini-2025-04-16 | Prompt Tokens: 1883 | Completion Tokens: 629 | Diff Range: 11f7224...fda456f

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

This review provides gentle AI-assisted feedback on your code. Insights are predictions rather than facts, so pick the ideas that work best for you. You remain in control, with AI here to support your choices.
Model: o4-mini-2025-04-16 | Prompt Tokens: 1156 | Completion Tokens: 1982 | Diff Range: 11f7224...fda456f

Comment thread pr-review/package.json Outdated
Comment on lines 32 to 44
"devDependencies": {
"@eslint/js": "9.39.4",
"@types/node": "24.12.4",
"@types/node": "24.13.1",
"@vercel/ncc": "0.38.4",
"eslint": "9.39.4",
"eslint-plugin-import": "2.32.0",
"eslint-plugin-sonarjs": "4.0.3",
"eslint-plugin-unicorn": "64.0.0",
"prettier": "3.8.3",
"tsx": "4.22.3",
"tsx": "4.22.4",
"typescript": "6.0.3",
"typescript-eslint": "8.59.4",
"typescript-eslint": "8.61.0",
"yaml": "2.9.0"

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

It’s better to use semantic version ranges (e.g., caret ^) rather than pinning exact versions. This allows you to receive backward-compatible patches automatically and helps with maintenance.

For example, you could update your devDependencies to:

"devDependencies": {
  "@eslint/js": "^9.39.4",
  "@types/node": "^24.13.1",
  "@vercel/ncc": "^0.38.4",
  "eslint": "^9.39.4",
  "eslint-plugin-import": "^2.32.0",
  "eslint-plugin-sonarjs": "^4.0.3",
  "eslint-plugin-unicorn": "^64.0.0",
  "prettier": "^3.8.3",
  "tsx": "^4.22.4",
  "typescript": "^6.0.3",
  "typescript-eslint": "^8.61.0",
  "yaml": "^2.9.0"
}

Comment thread pr-review/package.json Outdated
"tsx": "4.22.4",
"typescript": "6.0.3",
"typescript-eslint": "8.59.4",
"typescript-eslint": "8.61.0",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

The package typescript-eslint isn’t an official publish; you likely intended to use the scoped ESLint plugin and parser packages. Update to:

"devDependencies": {
  "@typescript-eslint/eslint-plugin": "^8.61.0",
  "@typescript-eslint/parser": "^8.61.0"
}

This ensures ESLint properly picks up your TypeScript rules and syntax parsing.

Comment thread pr-summary/package.json
Comment on lines 31 to 44
"devDependencies": {
"@eslint/js": "9.39.4",
"@types/node": "24.12.4",
"@types/node": "24.13.1",
"@vercel/ncc": "0.38.4",
"eslint": "9.39.4",
"eslint-plugin-import": "2.32.0",
"eslint-plugin-sonarjs": "4.0.3",
"eslint-plugin-unicorn": "64.0.0",
"prettier": "3.8.3",
"tsx": "4.22.3",
"tsx": "4.22.4",
"typescript": "6.0.3",
"typescript-eslint": "8.59.4",
"typescript-eslint": "8.61.0",
"yaml": "2.9.0"
}

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Since both pr-review and pr-summary share identical devDependencies, consider hoisting them to the workspace root package.json (if you’re using npm/yarn workspaces or pnpm). This reduces duplication and keeps versions consistent across packages.

Example in root package.json:

"workspaces": ["pr-review", "pr-summary"],
"devDependencies": {
  // move all shared devDependencies here
}

@renovate
renovate Bot force-pushed the renovate/non-major-dependencies branch from fda456f to 3b9af6a Compare June 9, 2026 17:15
@github-actions

github-actions Bot commented Jun 9, 2026

Copy link
Copy Markdown

Updated GitHub workflows to use the latest actions/checkout release and bumped various internal and development dependencies in both pr-review and pr-summary packages to their newest patch and minor versions.

Walkthrough

  • Chore: Upgraded actions/checkout steps from v6.0.2 to v6.0.3 across build and code-quality workflows.
  • Chore: Bumped @sap-ai-sdk/ai-api, @sap-ai-sdk/orchestration, and axios to 2.11.0 and 1.17.0 respectively.
  • Chore: Updated devDependencies (@types/node, @vercel/ncc, prettier, tsx, typescript-eslint) to their latest versions for improved tooling.

Model: o4-mini-2025-04-16 | Prompt Tokens: 1945 | Completion Tokens: 435 | Diff Range: fda456f...3b9af6a

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

We’ve put together a friendly code review with AI backed ideas to help you refine your work. These pointers are suggestions, not absolute truths. Feel free to choose what matches your style. You’re in charge of the final decisions and AI is here just to support your progress.
Model: o4-mini-2025-04-16 | Prompt Tokens: 1234 | Completion Tokens: 4105 | Diff Range: fda456f...3b9af6a

Comment thread pr-review/package.json Outdated
Comment on lines +33 to +35
"@eslint/js": "9.39.4",
"@types/node": "24.12.4",
"@vercel/ncc": "0.38.4",
"@types/node": "24.13.1",
"@vercel/ncc": "0.44.0",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

You updated several devDependency versions with exact pinned versions. To allow automatic non-breaking updates and avoid frequent manual bumps, consider using caret ranges. For example:

"devDependencies": {
  "@types/node": "^24.13.1",
  "@vercel/ncc": "^0.44.0",
  "prettier": "^3.8.4",
  "tsx": "^4.22.4",
  "typescript-eslint": "^8.61.0"
}

Comment thread pr-review/package.json Outdated
Comment on lines 32 to 44
"devDependencies": {
"@eslint/js": "9.39.4",
"@types/node": "24.12.4",
"@vercel/ncc": "0.38.4",
"@types/node": "24.13.1",
"@vercel/ncc": "0.44.0",
"eslint": "9.39.4",
"eslint-plugin-import": "2.32.0",
"eslint-plugin-sonarjs": "4.0.3",
"eslint-plugin-unicorn": "64.0.0",
"prettier": "3.8.3",
"tsx": "4.22.3",
"prettier": "3.8.4",
"tsx": "4.22.4",
"typescript": "6.0.3",
"typescript-eslint": "8.59.4",
"typescript-eslint": "8.61.0",
"yaml": "2.9.0"

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

The devDependencies section isn’t sorted, which can make diffs harder to read and maintain. Alphabetical ordering of keys improves readability and minimizes merge conflicts. For example:

"devDependencies": {
  "@eslint/js": "9.39.4",
  "@types/node": "24.13.1",
  "@vercel/ncc": "0.44.0",
  "eslint": "9.39.4",
  "eslint-plugin-import": "2.32.0",
  "eslint-plugin-sonarjs": "4.0.3",
  "eslint-plugin-unicorn": "64.0.0",
  "prettier": "3.8.4",
  "tsx": "4.22.4",
  "typescript": "6.0.3",
  "typescript-eslint": "8.61.0",
  "yaml": "2.9.0"
}

Comment thread pr-summary/package.json Outdated
Comment on lines +32 to +34
"@eslint/js": "9.39.4",
"@types/node": "24.12.4",
"@vercel/ncc": "0.38.4",
"@types/node": "24.13.1",
"@vercel/ncc": "0.44.0",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Similar to the other package, these dependencies are pinned exactly. Switching to caret ranges helps pick up compatible patches and minor updates automatically:

"devDependencies": {
  "@types/node": "^24.13.1",
  "@vercel/ncc": "^0.44.0",
  "prettier": "^3.8.4",
  "tsx": "^4.22.4",
  "typescript-eslint": "^8.61.0"
}

Comment thread pr-summary/package.json Outdated
Comment on lines 31 to 43
"devDependencies": {
"@eslint/js": "9.39.4",
"@types/node": "24.12.4",
"@vercel/ncc": "0.38.4",
"@types/node": "24.13.1",
"@vercel/ncc": "0.44.0",
"eslint": "9.39.4",
"eslint-plugin-import": "2.32.0",
"eslint-plugin-sonarjs": "4.0.3",
"eslint-plugin-unicorn": "64.0.0",
"prettier": "3.8.3",
"tsx": "4.22.3",
"prettier": "3.8.4",
"tsx": "4.22.4",
"typescript": "6.0.3",
"typescript-eslint": "8.59.4",
"typescript-eslint": "8.61.0",
"yaml": "2.9.0"

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

The devDependencies block is unsorted, which can complicate reviews. Keeping keys in alphabetical order ensures consistency:

"devDependencies": {
  "@eslint/js": "9.39.4",
  "@types-node": "24.13.1",
  "@vercel/ncc": "0.44.0",
  "eslint": "9.39.4",
  "eslint-plugin-import": "2.32.0",
  "eslint-plugin-sonarjs": "4.0.3",
  "eslint-plugin-unicorn": "64.0.0",
  "prettier": "3.8.4",
  "tsx": "4.22.4",
  "typescript": "6.0.3",
  "typescript-eslint": "8.61.0",
  "yaml": "2.9.0"
}

Comment thread pr-review/package.json
Comment on lines 31 to 46
},
"devDependencies": {
"@eslint/js": "9.39.4",
"@types/node": "24.12.4",
"@vercel/ncc": "0.38.4",
"@types/node": "24.13.1",
"@vercel/ncc": "0.44.0",
"eslint": "9.39.4",
"eslint-plugin-import": "2.32.0",
"eslint-plugin-sonarjs": "4.0.3",
"eslint-plugin-unicorn": "64.0.0",
"prettier": "3.8.3",
"tsx": "4.22.3",
"prettier": "3.8.4",
"tsx": "4.22.4",
"typescript": "6.0.3",
"typescript-eslint": "8.59.4",
"typescript-eslint": "8.61.0",
"yaml": "2.9.0"
}
}

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

The same devDependencies are repeated across both packages, which increases maintenance overhead and the chance of version drift. Consider adopting a shared configuration or npm workspaces to centralize these dependencies. For example, add at the root package.json:

{
  "workspaces": [
    "pr-review",
    "pr-summary"
  ],
  "devDependencies": {
    "@types/node": "^24.13.1",
    "@vercel/ncc": "^0.44.0",
    // ... other shared devDependencies
  }
}

@renovate
renovate Bot force-pushed the renovate/non-major-dependencies branch from 3b9af6a to 73972f6 Compare June 10, 2026 23:13
@github-actions

Copy link
Copy Markdown

Updated GitHub workflows to use the latest checkout action and bumped several package versions to pull in minor enhancements and fixes. No end-user functionality changed; this update keeps our CI/CD and SDKs up to date.

Walkthrough

  • Chore: Upgraded actions/checkout to v6.0.3 in build.yaml and code-quality.yaml
  • Chore: Bumped @sap-ai-sdk/ai-api, @sap-ai-sdk/orchestration, and axios in both pr-summary and pr-review
  • Chore: Updated devDependencies (@types/node, @vercel/ncc, prettier, tsx, typescript-eslint) for consistency and tooling improvements

Model: o4-mini-2025-04-16 | Prompt Tokens: 1945 | Completion Tokens: 300 | Diff Range: 3b9af6a...73972f6

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Thanks for sharing your code. I’ve provided some AI-powered suggestions to help you improve readability and functionality. Please treat these as optional recommendations rather than absolute rules. Feel free to adapt or ignore anything that doesn’t fit your style or goals. You know your project best, and your choices drive the final outcome—AI support is here to empower your process.
Model: o4-mini-2025-04-16 | Prompt Tokens: 1234 | Completion Tokens: 2408 | Diff Range: 3b9af6a...73972f6

Comment thread pr-review/package.json Outdated
Comment on lines +33 to +35
"@eslint/js": "9.39.4",
"@types/node": "24.12.4",
"@vercel/ncc": "0.38.4",
"@types/node": "24.13.2",
"@vercel/ncc": "0.44.0",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

I see that you’ve pinned several devDependencies to exact patch versions (e.g., "@types/node": "24.13.2", "@vercel/ncc": "0.44.0"). To allow non-breaking updates (bug fixes, performance improvements), consider using caret ranges. For example:

"devDependencies": {
  "@types/node": "^24.13.2",
  "@vercel/ncc": "^0.44.0",
  // ...other entries
}

This helps keep your tools up-to-date without frequent manual bumps.

Comment thread pr-summary/package.json Outdated
Comment on lines +32 to +34
"@eslint/js": "9.39.4",
"@types/node": "24.12.4",
"@vercel/ncc": "0.38.4",
"@types/node": "24.13.2",
"@vercel/ncc": "0.44.0",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Similar to the other package, you’re using exact versions for these devDependencies. Switching to caret ranges ensures you automatically pick up minor and patch releases, e.g.:

"devDependencies": {
  "@types/node": "^24.13.2",
  "@vercel/ncc": "^0.44.0",
  // ...
}

This approach reduces maintenance overhead while avoiding breaking changes.

Comment thread pr-review/package.json
Comment on lines 32 to 45
"devDependencies": {
"@eslint/js": "9.39.4",
"@types/node": "24.12.4",
"@vercel/ncc": "0.38.4",
"@types/node": "24.13.2",
"@vercel/ncc": "0.44.0",
"eslint": "9.39.4",
"eslint-plugin-import": "2.32.0",
"eslint-plugin-sonarjs": "4.0.3",
"eslint-plugin-unicorn": "64.0.0",
"prettier": "3.8.3",
"tsx": "4.22.3",
"prettier": "3.8.4",
"tsx": "4.22.4",
"typescript": "6.0.3",
"typescript-eslint": "8.59.4",
"typescript-eslint": "8.61.0",
"yaml": "2.9.0"
}

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Both pr-review and pr-summary share an identical set of devDependencies and version updates. To DRY up your configuration, consider hoisting these to a root package.json (using workspaces) or creating a shared ESLint/TypeScript config package. For example, in your monorepo root:

{
  "workspaces": ["pr-review", "pr-summary"],
  "devDependencies": {
    "eslint": "^9.39.4",
    "prettier": "^3.8.4",
    "typescript": "^6.0.3",
    // ...other shared tools
  }
}

Then reference them in child packages with:

"devDependencies": {
  "@your-scope/shared-config": "workspace:*",
  "tsx": "workspace:*
}

This ensures consistency and avoids duplicate version bumps across packages.

@renovate
renovate Bot force-pushed the renovate/non-major-dependencies branch from 73972f6 to 0de5008 Compare June 20, 2026 07:58
@github-actions

Copy link
Copy Markdown

Updated the GitHub CI workflows to use the latest checkout action and bumped core and dev dependencies across PR summarization and review packages to their newest minor releases, ensuring compatibility improvements and the latest bug fixes.

Walkthrough

  • Chore: Upgraded actions/checkout from v6.0.2 to v6.0.3 in build and code-quality workflows
  • Chore: Updated @sap-ai-sdk/ai-api, @sap-ai-sdk/orchestration, and axios to newer minor versions in both PR packages
  • Chore: Bumped devDependencies (@types/node, @vercel/ncc, eslint-plugin-sonarjs, prettier, tsx, typescript-eslint) for improved tooling and type support

Model: o4-mini-2025-04-16 | Prompt Tokens: 1979 | Completion Tokens: 628 | Diff Range: 73972f6...0de5008

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Enjoy a supportive code review powered by AI. Some insights are projections, not certainties, so feel free to adopt what resonates. Your judgment guides the outcome—AI is here to assist.
Model: o4-mini-2025-04-16 | Prompt Tokens: 1730 | Completion Tokens: 3021 | Diff Range: 73972f6...0de5008

Comment thread pr-review/package.json
Comment on lines -23 to 28
"@sap-ai-sdk/ai-api": "2.10.0",
"@sap-ai-sdk/orchestration": "2.10.0",
"axios": "1.16.1",
"@sap-ai-sdk/ai-api": "2.11.0",
"@sap-ai-sdk/orchestration": "2.11.0",
"axios": "1.18.0",
"minimatch": "10.2.5",
"mollitia": "0.2.0",
"octokit": "5.0.5",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Consider switching from fixed version pins to semver ranges (e.g. ^2.11.0) for your dependencies to automatically pick up non-breaking patch releases. Also, sorting the entries alphabetically improves readability and maintainability. For example:

"dependencies": {
  "@octokit/plugin-retry": "^8.1.0",
  "@octokit/plugin-throttling": "^11.0.3",
  "@octokit/webhooks": "^13.9.1",
  "@sap-ai-sdk/ai-api": "^2.11.0",
  "@sap-ai-sdk/orchestration": "^2.11.0",
  "axios": "^1.18.0",
  "minimatch": "^10.2.5",
  "mollitia": "^0.2.0",
  "octokit": "^5.0.5"
}

Comment thread pr-review/package.json Outdated
Comment on lines 34 to 44
"@types/node": "24.12.4",
"@vercel/ncc": "0.38.4",
"@types/node": "24.13.2",
"@vercel/ncc": "0.44.0",
"eslint": "9.39.4",
"eslint-plugin-import": "2.32.0",
"eslint-plugin-sonarjs": "4.0.3",
"eslint-plugin-sonarjs": "4.1.0",
"eslint-plugin-unicorn": "64.0.0",
"prettier": "3.8.3",
"tsx": "4.22.3",
"prettier": "3.8.4",
"tsx": "4.22.4",
"typescript": "6.0.3",
"typescript-eslint": "8.59.4",
"typescript-eslint": "8.61.1",
"yaml": "2.9.0"

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

After bumping devDependencies, regenerate and commit your lockfile (e.g., npm install or yarn install) to ensure consistent installs across environments. Additionally, consider specifying a Node.js engine range to prevent unexpected breakages:

"engines": {
  "node": ">=16.0.0 <19.0.0"
}

Comment thread pr-summary/package.json
Comment on lines -22 to 27
"@sap-ai-sdk/ai-api": "2.10.0",
"@sap-ai-sdk/orchestration": "2.10.0",
"axios": "1.16.1",
"@sap-ai-sdk/ai-api": "2.11.0",
"@sap-ai-sdk/orchestration": "2.11.0",
"axios": "1.18.0",
"minimatch": "10.2.5",
"mollitia": "0.2.0",
"octokit": "5.0.5",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

As with the other package, use semver ranges (^ or ~) instead of exact version pins and keep the list sorted alphabetically. This approach helps you automatically receive non-breaking updates and keeps the file tidy. For example:

"dependencies": {
  "@octokit/plugin-retry": "^8.1.0",
  "@octokit/plugin-throttling": "^11.0.3",
  "@octokit/webhooks": "^13.9.1",
  "@sap-ai-sdk/ai-api": "^2.11.0",
  "@sap-ai-sdk/orchestration": "^2.11.0",
  "axios": "^1.18.0",
  "minimatch": "^10.2.5",
  "mollitia": "^0.2.0",
  "octokit": "^5.0.5"
}

Comment thread pr-summary/package.json Outdated
Comment on lines 33 to 43
"@types/node": "24.12.4",
"@vercel/ncc": "0.38.4",
"@types/node": "24.13.2",
"@vercel/ncc": "0.44.0",
"eslint": "9.39.4",
"eslint-plugin-import": "2.32.0",
"eslint-plugin-sonarjs": "4.0.3",
"eslint-plugin-sonarjs": "4.1.0",
"eslint-plugin-unicorn": "64.0.0",
"prettier": "3.8.3",
"tsx": "4.22.3",
"prettier": "3.8.4",
"tsx": "4.22.4",
"typescript": "6.0.3",
"typescript-eslint": "8.59.4",
"typescript-eslint": "8.61.1",
"yaml": "2.9.0"

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Remember to update and commit the lockfile after bumping devDependencies. If these bumps include ESLint, Prettier, or TypeScript updates, run your linting and build scripts (e.g., npm run lint and npm run build) to catch any new issues early.

@renovate
renovate Bot force-pushed the renovate/non-major-dependencies branch from 0de5008 to 7513417 Compare June 21, 2026 09:48
@github-actions

Copy link
Copy Markdown

This update standardizes CI workflows and dependency versions across the project to ensure compatibility with the latest tools and libraries.

Walkthrough

  • Chore: Bumped actions/checkout to v7.0.0 in build and code-quality workflows for improved stability.
  • Chore: Upgraded SDKs (@sap-ai-sdk/ai-api, @sap-ai-sdk/orchestration) and Axios for minor enhancements and bug fixes.
  • Chore: Updated devDependencies (@types/node, @vercel/ncc, eslint-plugin-sonarjs, prettier, tsx, typescript-eslint) to current patch/minor releases.

Model: o4-mini-2025-04-16 | Prompt Tokens: 2014 | Completion Tokens: 604 | Diff Range: 0de5008...7513417

@renovate
renovate Bot force-pushed the renovate/non-major-dependencies branch from 7513417 to 09e481d Compare June 22, 2026 20:05
@github-actions

Copy link
Copy Markdown

Updated dependencies in both pr-review and pr-summary packages. Upgraded core AI SDK modules, HTTP client, build tools, and linting-related devDependencies to the latest minor and patch versions for better compatibility and developer experience.

Walkthrough

  • Chore: Bumped @sap-ai-sdk/ai-api & orchestration from 2.10.0 to 2.11.0 and axios from 1.16.1 to 1.18.1 to ensure up-to-date API integrations.
  • Chore: Upgraded devDependencies—including TypeScript, ESLint, Prettier, tsx, ncc, and eslint-plugin-sonarjs—to streamline builds and maintain code-quality standards.

Model: o4-mini-2025-04-16 | Prompt Tokens: 1070 | Completion Tokens: 806 | Diff Range: 7513417...09e481d

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Get a supportive review of your code powered by AI. Some tips are based on educated guesses and may not apply perfectly, so adapt them to your needs. You remain in control, with AI serving as a helpful resource.
Model: o4-mini-2025-04-16 | Prompt Tokens: 1730 | Completion Tokens: 2132 | Diff Range: 0de5008...09e481d

Comment thread pr-review/package.json Outdated
Comment on lines +23 to +25
"@sap-ai-sdk/ai-api": "2.10.0",
"@sap-ai-sdk/orchestration": "2.10.0",
"axios": "1.16.1",
"@sap-ai-sdk/ai-api": "2.11.0",
"@sap-ai-sdk/orchestration": "2.11.0",
"axios": "1.18.1",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Consider switching from fixed version pins to a caret (^) range for these SDK and Axios dependencies. This allows your project to automatically receive backward-compatible updates and security patches without manual bumps. For example:

{
  "dependencies": {
    "@sap-ai-sdk/ai-api": "^2.11.0",
    "@sap-ai-sdk/orchestration": "^2.11.0",
    "axios": "^1.18.1"
  }
}

This approach reduces maintenance overhead and improves security posture.

Comment thread pr-review/package.json Outdated
Comment on lines +34 to +43
"@types/node": "24.12.4",
"@vercel/ncc": "0.38.4",
"@types/node": "24.13.2",
"@vercel/ncc": "0.44.0",
"eslint": "9.39.4",
"eslint-plugin-import": "2.32.0",
"eslint-plugin-sonarjs": "4.0.3",
"eslint-plugin-sonarjs": "4.1.0",
"eslint-plugin-unicorn": "64.0.0",
"prettier": "3.8.3",
"tsx": "4.22.3",
"prettier": "3.8.4",
"tsx": "4.22.4",
"typescript": "6.0.3",
"typescript-eslint": "8.59.4",
"typescript-eslint": "8.62.0",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

DevDependencies have been updated to newer patch versions, but you might simplify upgrades by using caret (^) version ranges here as well. It ensures you pick up minor and patch fixes automatically. For instance:

- "@types/node": "24.13.2"
+ "@types/node": "^24.13.2"
- "@vercel/ncc": "0.44.0"
+ "@vercel/ncc": "^0.44.0"
- "eslint-plugin-sonarjs": "4.1.0"
+ "eslint-plugin-sonarjs": "^4.1.0"
- "prettier": "3.8.4"
+ "prettier": "^3.8.4"
- "tsx": "4.22.4"
+ "tsx": "^4.22.4"
- "typescript-eslint": "8.62.0"
+ "typescript-eslint": "^8.62.0"

Comment thread pr-summary/package.json Outdated
Comment on lines +22 to +24
"@sap-ai-sdk/ai-api": "2.10.0",
"@sap-ai-sdk/orchestration": "2.10.0",
"axios": "1.16.1",
"@sap-ai-sdk/ai-api": "2.11.0",
"@sap-ai-sdk/orchestration": "2.11.0",
"axios": "1.18.1",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Similar to the other package, consider using caret ranges for the bumped dependencies to receive non-breaking updates automatically. Example:

{
  "dependencies": {
    "@sap-ai-sdk/ai-api": "^2.11.0",
    "@sap-ai-sdk/orchestration": "^2.11.0",
    "axios": "^1.18.1"
  }
}

Comment thread pr-summary/package.json Outdated
Comment on lines +33 to +42
"@types/node": "24.12.4",
"@vercel/ncc": "0.38.4",
"@types/node": "24.13.2",
"@vercel/ncc": "0.44.0",
"eslint": "9.39.4",
"eslint-plugin-import": "2.32.0",
"eslint-plugin-sonarjs": "4.0.3",
"eslint-plugin-sonarjs": "4.1.0",
"eslint-plugin-unicorn": "64.0.0",
"prettier": "3.8.3",
"tsx": "4.22.3",
"prettier": "3.8.4",
"tsx": "4.22.4",
"typescript": "6.0.3",
"typescript-eslint": "8.59.4",
"typescript-eslint": "8.62.0",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Align devDependencies with caret ranges to reduce manual version management. For example:

- "@types/node": "24.13.2"
+ "@types/node": "^24.13.2"
- "@vercel/ncc": "0.44.0"
+ "@vercel/ncc": "^0.44.0"
- "eslint-plugin-sonarjs": "4.1.0"
+ "eslint-plugin-sonarjs": "^4.1.0"
- "prettier": "3.8.4"
+ "prettier": "^3.8.4"
- "tsx": "4.22.4"
+ "tsx": "^4.22.4"
- "typescript-eslint": "8.62.0"
+ "typescript-eslint": "^8.62.0"

@renovate
renovate Bot force-pushed the renovate/non-major-dependencies branch from 09e481d to b6724aa Compare June 24, 2026 08:52
@github-actions

Copy link
Copy Markdown

Dependency versions have been bumped across both pr-review and pr-summary packages to incorporate the latest AI SDK, HTTP client, and development tooling releases. These updates bring in minor feature improvements, bug fixes, and security patches without altering end-user functionality.

Walkthrough

  • Chore: Upgraded @sap-ai-sdk/ai-api and @sap-ai-sdk/orchestration from 2.10.0 to 2.12.0
  • Chore: Updated axios from 1.16.1 to 1.18.1 for improved request handling
  • Chore: Bumped devDependencies (@types/node, @vercel/ncc, eslint-plugin-sonarjs, prettier, tsx, typescript-eslint) to their latest patch versions for toolchain stability and code quality enhancements

Model: o4-mini-2025-04-16 | Prompt Tokens: 1070 | Completion Tokens: 709 | Diff Range: 09e481d...b6724aa

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

We’ve put together a supportive AI-assisted review of your code. These suggestions are ideas, not set in stone. Feel free to pick what suits your project. You’re the expert—AI is here to help you shine.
Model: o4-mini-2025-04-16 | Prompt Tokens: 1046 | Completion Tokens: 2706 | Diff Range: 09e481d...b6724aa

Comment thread pr-review/package.json Outdated
Comment on lines +23 to +25
"@sap-ai-sdk/ai-api": "2.10.0",
"@sap-ai-sdk/orchestration": "2.10.0",
"axios": "1.16.1",
"@sap-ai-sdk/ai-api": "2.12.0",
"@sap-ai-sdk/orchestration": "2.12.0",
"axios": "1.18.1",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

You’re currently pinning dependencies to exact versions, which can lead to manual updates for every minor or patch release. Consider using caret (^) ranges in your package.json to automatically receive non-breaking updates. For example:

"dependencies": {
  "@sap-ai-sdk/ai-api": "^2.12.0",
  "@sap-ai-sdk/orchestration": "^2.12.0",
  "axios": "^1.18.1"
}

Comment thread pr-review/package.json Outdated
Comment on lines 20 to 28
"@octokit/plugin-retry": "8.1.0",
"@octokit/plugin-throttling": "11.0.3",
"@octokit/webhooks": "13.9.1",
"@sap-ai-sdk/ai-api": "2.10.0",
"@sap-ai-sdk/orchestration": "2.10.0",
"axios": "1.16.1",
"@sap-ai-sdk/ai-api": "2.12.0",
"@sap-ai-sdk/orchestration": "2.12.0",
"axios": "1.18.1",
"minimatch": "10.2.5",
"mollitia": "0.2.0",
"octokit": "5.0.5",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

pr-review and pr-summary share many of the same dependencies at the same versions. In a monorepo setup, you can extract common dependencies into the root package.json and leverage workspaces to avoid duplication, simplify version management, and ensure consistency across packages. For example:

{
  "workspaces": ["pr-review", "pr-summary"],
  "dependencies": {
    "@sap-ai-sdk/ai-api": "^2.12.0",
    "@sap-ai-sdk/orchestration": "^2.12.0",
    "axios": "^1.18.1"
  }
}

Comment thread pr-summary/package.json Outdated
Comment on lines +22 to +24
"@sap-ai-sdk/ai-api": "2.10.0",
"@sap-ai-sdk/orchestration": "2.10.0",
"axios": "1.16.1",
"@sap-ai-sdk/ai-api": "2.12.0",
"@sap-ai-sdk/orchestration": "2.12.0",
"axios": "1.18.1",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

You’re currently pinning dependencies to exact versions, which can lead to manual updates for every minor or patch release. Consider using caret (^) ranges in your package.json to automatically receive non-breaking updates. For example:

"dependencies": {
  "@sap-ai-sdk/ai-api": "^2.12.0",
  "@sap-ai-sdk/orchestration": "^2.12.0",
  "axios": "^1.18.1"
}

Comment thread pr-summary/package.json Outdated
Comment on lines 19 to 27
"@octokit/plugin-retry": "8.1.0",
"@octokit/plugin-throttling": "11.0.3",
"@octokit/webhooks": "13.9.1",
"@sap-ai-sdk/ai-api": "2.10.0",
"@sap-ai-sdk/orchestration": "2.10.0",
"axios": "1.16.1",
"@sap-ai-sdk/ai-api": "2.12.0",
"@sap-ai-sdk/orchestration": "2.12.0",
"axios": "1.18.1",
"minimatch": "10.2.5",
"mollitia": "0.2.0",
"octokit": "5.0.5",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

pr-summary and pr-review share many of the same dependencies at the same versions. In a monorepo setup, you can extract common dependencies into the root package.json and leverage workspaces to avoid duplication, simplify version management, and ensure consistency across packages. For example:

{
  "workspaces": ["pr-review", "pr-summary"],
  "dependencies": {
    "@sap-ai-sdk/ai-api": "^2.12.0",
    "@sap-ai-sdk/orchestration": "^2.12.0",
    "axios": "^1.18.1"
  }
}

@renovate
renovate Bot force-pushed the renovate/non-major-dependencies branch from 6122133 to 11df4fe Compare September 11, 2026 21:05
@github-actions

Copy link
Copy Markdown

The CI workflows have been updated to use the latest GitHub Actions versions for both checkout and Node setup, ensuring compatibility and bug fixes. Meanwhile, the PR summary and review packages received multiple dependency bumps across core libraries, SDKs, and developer tools to incorporate improvements and security patches.

Walkthrough

  • Chore: Upgraded actions/checkout to v7.0.1 and actions/setup-node to v6.5.0 in build and code-quality workflows.
  • Chore: Bumped runtime and dev dependencies in pr-summary and pr-review packages (Octokit plugins, SAP AI SDKs, ESLint, Prettier, TypeScript tools, etc.).

Model: o4-mini-2025-04-16 | Prompt Tokens: 2669 | Completion Tokens: 608 | Diff Range: 6122133...11df4fe

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Here’s a warm review of your code enriched by AI support. These ideas are thoughtful suggestions, not hard rules, so feel free to apply what works best for your project. You’re in charge and AI is here to lend a hand.

Model: o4-mini-2025-04-16 | Prompt Tokens: 2108 | Completion Tokens: 3798 | Diff Range: 6122133...11df4fe

Comment thread pr-review/package.json
Comment on lines -20 to +21
"@octokit/plugin-retry": "8.1.0",
"@octokit/plugin-throttling": "11.0.3",
"@octokit/plugin-retry": "8.1.1",
"@octokit/plugin-throttling": "11.0.5",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

We have multiple version bumps for @octokit plugins here. To avoid duplicating versions across workspaces, consider extracting shared dependency versions into your root package or leveraging an NPM/Yarn "resolutions" field. For example:

// in root package.json
"resolutions": {
  "@octokit/plugin-retry": "8.1.1",
  "@octokit/plugin-throttling": "11.0.5"
}

This ensures all sub-packages inherit consistent versions and reduces maintenance overhead.

Comment thread pr-review/package.json
"minimatch": "10.2.5",
"minimatch": "10.2.6",
"mollitia": "0.2.0",
"octokit": "5.0.5",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

The standalone octokit package at version 5.0.5 is very dated compared to the other Octokit plugins. Consider replacing it with the modern scoped package and aligning versions. For example:

"dependencies": {
  "@octokit/rest": "19.0.7"
}

Comment thread pr-review/package.json
Comment on lines -43 to +44
"typescript-eslint": "8.59.4",
"yaml": "2.9.0"
"typescript-eslint": "8.70.0",
"yaml": "2.9.1"

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

The unscoped typescript-eslint is not an official package on npm. You likely need to install the scoped parser and plugin:

"devDependencies": {
  "@typescript-eslint/parser": "8.70.0",
  "@typescript-eslint/eslint-plugin": "8.70.0"
}

Comment thread pr-review/package.json Outdated
Comment on lines +23 to +24
"@sap-ai-sdk/ai-api": "2.10.0",
"@sap-ai-sdk/orchestration": "2.10.0",
"@sap-ai-sdk/ai-api": "2.15.0",
"@sap-ai-sdk/orchestration": "2.15.0",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

You bumped @sap-ai-sdk/ai-api and @sap-ai-sdk/orchestration from 2.10.0 to 2.15.0. Review the SDK changelog for breaking changes or required initialization updates. For example, if new options were added:

import { Orchestration } from '@sap-ai-sdk/orchestration';
const orch = new Orchestration({ timeout: 5000, enableLogging: true });

Comment thread pr-summary/package.json
Comment on lines -19 to +20
"@octokit/plugin-retry": "8.1.0",
"@octokit/plugin-throttling": "11.0.3",
"@octokit/plugin-retry": "8.1.1",
"@octokit/plugin-throttling": "11.0.5",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Mirroring the other workspace, you’re updating @octokit plugins here. To maintain consistency and follow DRY principles, pin these versions at the root or use a "resolutions" block:

"resolutions": {
  "@octokit/plugin-retry": "8.1.1",
  "@octokit/plugin-throttling": "11.0.5"
}

Comment thread pr-summary/package.json
"minimatch": "10.2.5",
"minimatch": "10.2.6",
"mollitia": "0.2.0",
"octokit": "5.0.5",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Consider replacing the legacy octokit package with @octokit/rest (or the unified Octokit client) to stay aligned with current Octokit conventions:

"dependencies": {
  "@octokit/rest": "19.0.7"
}

Comment thread pr-summary/package.json
Comment on lines -42 to +43
"typescript-eslint": "8.59.4",
"yaml": "2.9.0"
"typescript-eslint": "8.70.0",
"yaml": "2.9.1"

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

The typescript-eslint entry here is incorrect; use the scoped parser and plugin packages instead:

"devDependencies": {
  "@typescript-eslint/parser": "8.70.0",
  "@typescript-eslint/eslint-plugin": "8.70.0"
}

Comment thread pr-summary/package.json Outdated
Comment on lines +22 to +23
"@sap-ai-sdk/ai-api": "2.10.0",
"@sap-ai-sdk/orchestration": "2.10.0",
"@sap-ai-sdk/ai-api": "2.15.0",
"@sap-ai-sdk/orchestration": "2.15.0",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

You’ve updated the SAP AI SDKs to 2.15.0 here as well. Please audit your code for any required changes—such as new constructor arguments or config properties—and ensure tests cover the updated behavior.

@renovate
renovate Bot force-pushed the renovate/non-major-dependencies branch from 11df4fe to 6e8de9d Compare September 13, 2026 01:13
@github-actions

Copy link
Copy Markdown

This update refreshes CI workflows and internal tooling by bumping GitHub Actions versions and upgrading various Node dependencies to their latest patch releases, ensuring more stable builds and up-to-date libraries.

Walkthrough

  • Chore: Upgraded actions/checkout to v7.0.1 and actions/setup-node to v6.5.0 across build and code-quality workflows.
  • Chore: Bumped core SDKs and plugins in both pr-summary and pr-review packages, including Octokit retry/throttling, SAP AI SDK, and Zod.
  • Chore: Updated dev tooling—ESLint, Prettier, TypeScript, and related plugins—to their latest versions.

Model: o4-mini-2025-04-16 | Prompt Tokens: 2669 | Completion Tokens: 425 | Diff Range: 11df4fe...6e8de9d

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

I’ve provided a friendly review of your code with AI-powered suggestions. These ideas are meant as guidance rather than fixed rules, so choose what best fits your project. You remain in control of every decision—AI is simply here to support your work.

Model: o4-mini-2025-04-16 | Prompt Tokens: 2108 | Completion Tokens: 2353 | Diff Range: 11df4fe...6e8de9d

Comment thread pr-review/package.json
Comment on lines -20 to +21
"@octokit/plugin-retry": "8.1.0",
"@octokit/plugin-throttling": "11.0.3",
"@octokit/plugin-retry": "8.1.1",
"@octokit/plugin-throttling": "11.0.5",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

It’s generally a better practice to use version ranges (e.g., caret ^) instead of pinning exact versions. This allows your project to receive non-breaking patch updates automatically while still locking down major changes. For example, you could update your Octokit plugins like this:

"dependencies": {
  "@octokit/plugin-retry": "^8.1.1",
  "@octokit/plugin-throttling": "^11.0.5",
  // ...rest of dependencies
}

Comment thread pr-summary/package.json
Comment on lines -19 to +20
"@octokit/plugin-retry": "8.1.0",
"@octokit/plugin-throttling": "11.0.3",
"@octokit/plugin-retry": "8.1.1",
"@octokit/plugin-throttling": "11.0.5",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

As in the other package, consider swapping exact versions for caret ranges to pick up patch releases automatically. For example:

"dependencies": {
  "@octokit/plugin-retry": "^8.1.1",
  "@octokit/plugin-throttling": "^11.0.5",
  // ...rest of dependencies
}

Comment thread pr-review/package.json
Comment on lines 32 to +44
"devDependencies": {
"@eslint/js": "9.39.4",
"@types/node": "24.12.4",
"@vercel/ncc": "0.38.4",
"eslint": "9.39.4",
"@eslint/js": "9.39.5",
"@types/node": "24.13.4",
"@vercel/ncc": "0.45.0",
"eslint": "9.39.5",
"eslint-plugin-import": "2.32.0",
"eslint-plugin-sonarjs": "4.0.3",
"eslint-plugin-sonarjs": "4.2.0",
"eslint-plugin-unicorn": "64.0.0",
"prettier": "3.8.3",
"tsx": "4.22.3",
"prettier": "3.9.6",
"tsx": "4.23.13",
"typescript": "6.0.3",
"typescript-eslint": "8.59.4",
"yaml": "2.9.0"
"typescript-eslint": "8.70.0",
"yaml": "2.9.1"

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

The dependencies and devDependencies sections could be sorted alphabetically. Alphabetical ordering improves readability and makes it easier to find dependencies when you come back later. Here’s an example reordering your devDependencies:

-  "devDependencies": {
-    "@vercel/ncc": "0.45.0",
-    "@types/node": "24.13.4",
-    "@eslint/js": "9.39.5",
-    "eslint": "9.39.5",
-    // ...
-    "yaml": "2.9.1"
-  }
+  "devDependencies": {
+    "@eslint/js": "9.39.5",
+    "@types/node": "24.13.4",
+    "@vercel/ncc": "0.45.0",
+    "eslint": "9.39.5",
+    // ...
+    "yaml": "2.9.1"
+  }

Comment thread pr-review/package.json
@@ -17,30 +17,30 @@
"@actions/core": "3.0.1",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

You may want to specify an engines field to enforce a consistent Node.js version across environments. This helps avoid "it works on my machine" issues. For example:

"engines": {
  "node": ">=16.0.0 <19.0.0"
},
"dependencies": { ... }

Comment thread pr-summary/package.json Outdated
Comment on lines +16 to +29
"dependencies": {
"@actions/core": "3.0.1",
"@actions/github": "9.1.1",
"@octokit/plugin-retry": "8.1.0",
"@octokit/plugin-throttling": "11.0.3",
"@octokit/plugin-retry": "8.1.1",
"@octokit/plugin-throttling": "11.0.5",
"@octokit/webhooks": "13.9.1",
"@sap-ai-sdk/ai-api": "2.10.0",
"@sap-ai-sdk/orchestration": "2.10.0",
"@sap-ai-sdk/ai-api": "2.15.0",
"@sap-ai-sdk/orchestration": "2.15.0",
"axios": "1.16.1",
"minimatch": "10.2.5",
"minimatch": "10.2.6",
"mollitia": "0.2.0",
"octokit": "5.0.5",
"parse-diff": "0.12.0",
"zod": "4.4.3"
"zod": "4.6.4"

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

pr-summary and pr-review share almost identical dependencies and devDependencies. To reduce duplication and ensure consistent versions, consider extracting common dependencies into a shared workspace or using a monorepo tool (e.g., Yarn Workspaces, npm workspaces). This will make maintenance easier as you only bump versions in one place.

@renovate
renovate Bot force-pushed the renovate/non-major-dependencies branch from 6e8de9d to 67c0ab2 Compare September 14, 2026 02:37
@github-actions

Copy link
Copy Markdown

This update standardizes CI configurations by bumping GitHub Actions steps to their latest patch versions and refreshes all core and development dependencies in both pr-summary and pr-review packages. This ensures improved build stability, linting accuracy, and compatibility with the newest SDK features.

Walkthrough

  • Chore: Upgraded actions/checkout to v7.0.1 across workflows for consistent branch handling.
  • Chore: Updated actions/setup-node to v6.5.0 to align with current Node configuration.
  • Chore: Bumped Octokit plugins, SAP AI SDK, minimatch, and Zod to latest patches for reliability.
  • Chore: Refreshed linting and build tools (ESLint, Prettier, TypeScript, TSX, NCC) to ensure up-to-date developer experience.

Model: o4-mini-2025-04-16 | Prompt Tokens: 2669 | Completion Tokens: 958 | Diff Range: 6e8de9d...67c0ab2

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Here is a friendly code review powered by AI. Consider these suggestions as possibilities, not fixed rules. Use what fits your style and needs. You remain in control of every decision—AI is just a supportive tool here to help.

Model: o4-mini-2025-04-16 | Prompt Tokens: 2108 | Completion Tokens: 2065 | Diff Range: 6e8de9d...67c0ab2

Comment thread pr-review/package.json
Comment on lines -20 to +21
"@octokit/plugin-retry": "8.1.0",
"@octokit/plugin-throttling": "11.0.3",
"@octokit/plugin-retry": "8.1.1",
"@octokit/plugin-throttling": "11.0.5",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

I see you’ve pinned both @octokit/plugin-retry and @octokit/plugin-throttling to exact versions. Pinning to exact patch revisions can help reproducibility, but it also means you’ll need to manually bump them for every minor fix. Consider using a semver range (e.g., ^8.1.1 and ^11.0.5) to automatically receive non-breaking updates:

{
  "dependencies": {
    "@octokit/plugin-retry": "^8.1.1",
    "@octokit/plugin-throttling": "^11.0.5"
  }
}

This gives you the latest compatible patch releases without sacrificing stability.

Comment thread pr-summary/package.json
Comment on lines -19 to +20
"@octokit/plugin-retry": "8.1.0",
"@octokit/plugin-throttling": "11.0.3",
"@octokit/plugin-retry": "8.1.1",
"@octokit/plugin-throttling": "11.0.5",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Similar to the other package, you’re pinning retry and throttling plugins exactly. Using a caret range (e.g., ^8.1.1 and ^11.0.5) can simplify maintenance and ensure you don’t miss important patch fixes. For example:

{
  "dependencies": {
    "@octokit/plugin-retry": "^8.1.1",
    "@octokit/plugin-throttling": "^11.0.5"
  }
}

Comment thread pr-review/package.json
Comment on lines 27 to 29
"mollitia": "0.2.0",
"octokit": "5.0.5",
"parse-diff": "0.12.0",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

I notice you’re including both the legacy octokit package and the newer scoped plugins (@octokit/*). If you’re not directly using the old octokit import, you might safely remove it to reduce bundle size and avoid confusion:

- "octokit": "5.0.5",

Double-check your codebase and CI tests to confirm nothing breaks after removal.

Comment thread pr-summary/package.json
Comment on lines -32 to +35
"@eslint/js": "9.39.4",
"@types/node": "24.12.4",
"@vercel/ncc": "0.38.4",
"eslint": "9.39.4",
"@eslint/js": "9.39.5",
"@types/node": "24.13.4",
"@vercel/ncc": "0.45.0",
"eslint": "9.39.5",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Your devDependencies share the same versions between these two packages. Consider hoisting common devDependencies to the monorepo root (if you have one) or extracting them to a shared config. This reduces duplication and ensures consistency. For instance, in your root package.json:

{
  "devDependencies": {
    "eslint": "^9.39.5",
    "@types/node": "^24.13.4",
    "@vercel/ncc": "^0.45.0"
  }
}

Then remove them from individual package.json files and adjust your CI scripts accordingly.

@renovate
renovate Bot force-pushed the renovate/non-major-dependencies branch from 67c0ab2 to 9e35940 Compare September 15, 2026 18:38
@github-actions

Copy link
Copy Markdown

This update upgrades GitHub Actions workflows to use the latest checkout (v7.0.1) and setup-node (v6.5.0) actions, and refreshes PR summary and review package dependencies to current patch versions.

Walkthrough

  • Chore: Upgraded actions/checkout and actions/setup-node in build and code-quality workflows for improved CI stability.
  • Chore: Bumped core package dependencies (Octokit plugins, SAP AI SDK, zod, minimatch) in PR summary and review for latest fixes and security patches.
  • Chore: Updated development tools (ESLint, Prettier, TypeScript, ncc, etc.) to maintain compatibility and code quality.

Model: o4-mini-2025-04-16 | Prompt Tokens: 2669 | Completion Tokens: 1444 | Diff Range: 67c0ab2...9e35940

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Below is a friendly review of your code supported by AI insights. Some comments are educated guesses rather than certainties, so use what resonates most. Your expertise guides the final decisions and the AI is here to help you bring your ideas to life.

Model: o4-mini-2025-04-16 | Prompt Tokens: 2108 | Completion Tokens: 2409 | Diff Range: 67c0ab2...9e35940

Comment thread pr-review/package.json
Comment on lines -20 to +21
"@octokit/plugin-retry": "8.1.0",
"@octokit/plugin-throttling": "11.0.3",
"@octokit/plugin-retry": "8.1.1",
"@octokit/plugin-throttling": "11.0.5",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Consider using caret (^) version ranges for your dependencies rather than pinning to an exact version. This allows non-breaking (minor and patch) updates to be installed automatically, improving maintainability and reducing churn when security fixes are released. For example:

// Before
"@octokit/plugin-retry": "8.1.1",
"@octokit/plugin-throttling": "11.0.5",

// After
"@octokit/plugin-retry": "^8.1.1",
"@octokit/plugin-throttling": "^11.0.5",

Apply the same pattern to the other dependencies you’re frequently bumping, like @sap-ai-sdk/*, minimatch, and zod. This strategy keeps you on secure, up-to-date versions without manually updating every patch.

Comment thread pr-review/package.json
"minimatch": "10.2.5",
"minimatch": "10.2.6",
"mollitia": "0.2.0",
"octokit": "5.0.5",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

The standalone octokit package (5.0.5) is the legacy entrypoint for Octokit REST v5 and may overlap with your scoped @octokit/* dependencies. To reduce bundle size and avoid confusion, consider removing this entry if you’re exclusively using the newer @octokit libraries. For instance:

- "octokit": "5.0.5",

Comment thread pr-review/package.json
Comment on lines -43 to +44
"typescript-eslint": "8.59.4",
"yaml": "2.9.0"
"typescript-eslint": "8.70.0",
"yaml": "2.9.1"

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

The typescript-eslint package name here doesn’t match the official scoped packages. You likely need:

"devDependencies": {
  "@typescript-eslint/parser": "^8.70.0",
  "@typescript-eslint/eslint-plugin": "^8.70.0",
  // remove the incorrect "typescript-eslint" entry
}

This ensures ESLint can parse TypeScript correctly and apply the recommended rules.

Comment thread pr-summary/package.json
Comment on lines -19 to +20
"@octokit/plugin-retry": "8.1.0",
"@octokit/plugin-throttling": "11.0.3",
"@octokit/plugin-retry": "8.1.1",
"@octokit/plugin-throttling": "11.0.5",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Consider using caret (^) version ranges for your dependencies rather than pinning to an exact version. This allows non-breaking (minor and patch) updates to be installed automatically, improving maintainability and reducing churn when security fixes are released. For example:

// Before
"@octokit/plugin-retry": "8.1.1",
"@octokit/plugin-throttling": "11.0.5",

// After
"@octokit/plugin-retry": "^8.1.1",
"@octokit/plugin-throttling": "^11.0.5",

Apply the same pattern to the other dependencies you’re frequently bumping, like @sap-ai-sdk/*, minimatch, and zod. This strategy keeps you on secure, up-to-date versions without manually updating every patch.

Comment thread pr-summary/package.json
"minimatch": "10.2.5",
"minimatch": "10.2.6",
"mollitia": "0.2.0",
"octokit": "5.0.5",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

The standalone octokit package (5.0.5) is the legacy entrypoint for Octokit REST v5 and may overlap with your scoped @octokit/* dependencies. To reduce bundle size and avoid confusion, consider removing this entry if you’re exclusively using the newer @octokit libraries. For instance:

- "octokit": "5.0.5",

Comment thread pr-summary/package.json
Comment on lines -42 to +43
"typescript-eslint": "8.59.4",
"yaml": "2.9.0"
"typescript-eslint": "8.70.0",
"yaml": "2.9.1"

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

The typescript-eslint package name here doesn’t match the official scoped packages. You likely need:

"devDependencies": {
  "@typescript-eslint/parser": "^8.70.0",
  "@typescript-eslint/eslint-plugin": "^8.70.0",
  // remove the incorrect "typescript-eslint" entry
}

This ensures ESLint can parse TypeScript correctly and apply the recommended rules.

@renovate
renovate Bot force-pushed the renovate/non-major-dependencies branch from 9e35940 to cebd247 Compare September 16, 2026 01:33
@github-actions

Copy link
Copy Markdown

This update bumps GitHub Action steps and project libraries to their latest patch versions, enhancing build reliability and incorporating recent fixes without altering user-facing behavior.

Walkthrough

  • Chore: Updated actions/checkout to v7.0.1 and actions/setup-node to v6.5.0 across CI workflows for improved stability.
  • Chore: Upgraded core dependencies in pr-summary and pr-review (octokit plugins, SAP AI SDKs, zod, minimatch) to benefit from recent fixes.
  • Chore: Refreshed devDependencies (ESLint, Prettier, TypeScript, ncc, plugins) to align linting/build tools with current standards.

Model: o4-mini-2025-04-16 | Prompt Tokens: 2669 | Completion Tokens: 1184 | Diff Range: 9e35940...cebd247

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Here’s a friendly review of your code enhanced by AI assistance. Some suggestions are based on patterns and may not apply in every context. Feel free to adopt what feels right for your project. You drive the decisions and AI is here to support your creativity and expertise.

Model: o4-mini-2025-04-16 | Prompt Tokens: 2108 | Completion Tokens: 2864 | Diff Range: 9e35940...cebd247

Comment thread pr-review/package.json
Comment on lines -20 to +21
"@octokit/plugin-retry": "8.1.0",
"@octokit/plugin-throttling": "11.0.3",
"@octokit/plugin-retry": "8.1.1",
"@octokit/plugin-throttling": "11.0.5",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Consider using caret (^) version ranges instead of pinning exact versions. This allows non-breaking upgrades automatically and reduces maintenance overhead. For example:

"dependencies": {
  "@octokit/plugin-retry": "^8.1.1",
  "@octokit/plugin-throttling": "^11.0.5",
  // …other deps
}

Comment thread pr-review/package.json
Comment on lines 17 to 31
"@actions/core": "3.0.1",
"@actions/github": "9.1.1",
"@octokit/action": "7.0.2",
"@octokit/plugin-retry": "8.1.0",
"@octokit/plugin-throttling": "11.0.3",
"@octokit/plugin-retry": "8.1.1",
"@octokit/plugin-throttling": "11.0.5",
"@octokit/webhooks": "13.9.1",
"@sap-ai-sdk/ai-api": "2.10.0",
"@sap-ai-sdk/orchestration": "2.10.0",
"@sap-ai-sdk/ai-api": "2.15.0",
"@sap-ai-sdk/orchestration": "2.15.0",
"axios": "1.16.1",
"minimatch": "10.2.5",
"minimatch": "10.2.6",
"mollitia": "0.2.0",
"octokit": "5.0.5",
"parse-diff": "0.12.0",
"zod": "4.4.3"
"zod": "4.6.5"
},

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Sort the entries in the dependencies block alphabetically to improve readability and make it easier to spot missing or duplicated entries. For example:

 "dependencies": {
-  "@actions/core": "3.0.1",
-  "@actions/github": "9.1.1",
+  "@actions/github": "9.1.1",
+  "@actions/core":  "3.0.1",
   // …other deps sorted alphabetically
 }

Comment thread pr-review/package.json
"typescript-eslint": "8.70.0",
"yaml": "2.9.1"
}
}

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Adding an engines field helps enforce a minimum Node.js version and communicates compatibility to contributors and CI systems. For example:

"engines": {
  "node": ">=14.0.0"
}

Comment thread pr-summary/package.json
Comment on lines -19 to +20
"@octokit/plugin-retry": "8.1.0",
"@octokit/plugin-throttling": "11.0.3",
"@octokit/plugin-retry": "8.1.1",
"@octokit/plugin-throttling": "11.0.5",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Consider using caret (^) version ranges for dependencies to allow non-breaking updates without manual version bumps. For example:

"dependencies": {
  "@octokit/plugin-retry": "^8.1.1",
  "@octokit/plugin-throttling": "^11.0.5",
  // …other deps
}

Comment thread pr-summary/package.json
Comment on lines 16 to 30
"dependencies": {
"@actions/core": "3.0.1",
"@actions/github": "9.1.1",
"@octokit/plugin-retry": "8.1.0",
"@octokit/plugin-throttling": "11.0.3",
"@octokit/plugin-retry": "8.1.1",
"@octokit/plugin-throttling": "11.0.5",
"@octokit/webhooks": "13.9.1",
"@sap-ai-sdk/ai-api": "2.10.0",
"@sap-ai-sdk/orchestration": "2.10.0",
"@sap-ai-sdk/ai-api": "2.15.0",
"@sap-ai-sdk/orchestration": "2.15.0",
"axios": "1.16.1",
"minimatch": "10.2.5",
"minimatch": "10.2.6",
"mollitia": "0.2.0",
"octokit": "5.0.5",
"parse-diff": "0.12.0",
"zod": "4.4.3"
"zod": "4.6.5"
},

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Alphabetize the entries in the dependencies section. This consistent ordering makes reviews faster and reduces merge conflicts. For example:

 "dependencies": {
-  "@actions/core": "3.0.1",
-  "@actions/github": "9.1.1",
+  "@actions/github": "9.1.1",
+  "@actions/core":  "3.0.1",
   // …other deps sorted alphabetically
 }

Comment thread pr-summary/package.json
"typescript-eslint": "8.70.0",
"yaml": "2.9.1"
}
}

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Include an engines field to explicitly declare the supported Node.js runtime version. This ensures consistency across environments:

"engines": {
  "node": ">=14.0.0"
}

@renovate
renovate Bot force-pushed the renovate/non-major-dependencies branch from cebd247 to 64fdef0 Compare September 16, 2026 09:07
@github-actions

Copy link
Copy Markdown

The CI workflows have been updated to use the latest GitHub Actions versions, and all packages in the pr-summary and pr-review modules have had their dependencies refreshed. These maintenance updates deliver improved stability, security patches, and performance optimizations without changing any end-user functionality.

Walkthrough

  • Chore: Upgraded actions/checkout to v7.0.1 and actions/setup-node to v6.5.0 in build and code-quality workflows for more reliable builds.
  • Chore: Bumped core and dev dependencies (e.g., Octokit plugins, SAP AI SDK, Prettier, TypeScript tools) in both pr-summary and pr-review packages to their latest releases.

Model: o4-mini-2025-04-16 | Prompt Tokens: 2669 | Completion Tokens: 675 | Diff Range: cebd247...64fdef0

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Here is a gentle AI-assisted review of your code. These insights are suggestions, not guarantees, so feel free to adopt what works best for your goals and style. Your expertise guides the project, with AI available to support you at every step.

Model: o4-mini-2025-04-16 | Prompt Tokens: 2108 | Completion Tokens: 4160 | Diff Range: cebd247...64fdef0

Comment thread pr-review/package.json
Comment on lines -20 to +21
"@octokit/plugin-retry": "8.1.0",
"@octokit/plugin-throttling": "11.0.3",
"@octokit/plugin-retry": "8.1.1",
"@octokit/plugin-throttling": "11.0.5",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

You’re currently pinning the Octokit plugins to exact versions (8.1.1 and 11.0.5). Consider using a caret range to automatically receive future patch releases without manual bumps:

"@octokit/plugin-retry": "^8.1.1",
"@octokit/plugin-throttling": "^11.0.5",

Comment thread pr-review/package.json Outdated
Comment on lines +23 to +24
"@sap-ai-sdk/ai-api": "2.10.0",
"@sap-ai-sdk/orchestration": "2.10.0",
"@sap-ai-sdk/ai-api": "2.15.0",
"@sap-ai-sdk/orchestration": "2.15.0",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

The @sap-ai-sdk modules were upgraded from 2.10.0 to 2.15.0. Before locking to this minor version, verify there are no breaking changes by checking the SDK changelog or adding a quick integration test. If you don’t need strict pinning, switch to a caret range:

"@sap-ai-sdk/ai-api": "^2.15.0",
"@sap-ai-sdk/orchestration": "^2.15.0",

Comment thread pr-review/package.json
Comment on lines -33 to +36
"@eslint/js": "9.39.4",
"@types/node": "24.12.4",
"@vercel/ncc": "0.38.4",
"eslint": "9.39.4",
"@eslint/js": "9.39.5",
"@types/node": "24.13.5",
"@vercel/ncc": "0.45.0",
"eslint": "9.39.5",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

You’ve bumped several devDependencies (@eslint/js, eslint, @vercel/ncc, @types/node, etc.). If this package doesn’t actually use TypeScript or some of these tools, consider removing unused entries to slim install times. Alternatively, move shared devDependencies to a root workspace to avoid duplication across packages.

Comment thread pr-summary/package.json
Comment on lines -19 to +20
"@octokit/plugin-retry": "8.1.0",
"@octokit/plugin-throttling": "11.0.3",
"@octokit/plugin-retry": "8.1.1",
"@octokit/plugin-throttling": "11.0.5",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Same pattern here: consider using caret ranges for the Octokit plugins to reduce future maintenance:

"@octokit/plugin-retry": "^8.1.1",
"@octokit/plugin-throttling": "^11.0.5",

Comment thread pr-summary/package.json Outdated
Comment on lines +22 to +23
"@sap-ai-sdk/ai-api": "2.15.0",
"@sap-ai-sdk/orchestration": "2.15.0",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Ensure that bumping @sap-ai-sdk from 2.10.0 to 2.15.0 doesn’t introduce breaking changes. Use a caret range to stay up to date with patch fixes:

"@sap-ai-sdk/ai-api": "^2.15.0",
"@sap-ai-sdk/orchestration": "^2.15.0",

Comment thread pr-summary/package.json
Comment on lines -32 to +35
"@eslint/js": "9.39.4",
"@types/node": "24.12.4",
"@vercel/ncc": "0.38.4",
"eslint": "9.39.4",
"@eslint/js": "9.39.5",
"@types/node": "24.13.5",
"@vercel/ncc": "0.45.0",
"eslint": "9.39.5",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Your devDependencies mirror the other package. To enforce consistency and reduce maintenance overhead, consider consolidating shared dev tooling in the monorepo root (or a shared package) instead of duplicating entries.

@renovate
renovate Bot force-pushed the renovate/non-major-dependencies branch from 64fdef0 to 7bd5013 Compare September 17, 2026 23:37
@github-actions

Copy link
Copy Markdown

Updated CI workflows to use the latest actions versions and bumped multiple core and dev dependencies in the PR summary and review packages to their newest patch releases.

Walkthrough

  • Chore: Upgraded actions/checkout from v7.0.0 to v7.0.1 and actions/setup-node from v6.4.0 to v6.5.0 across all build and code-quality workflows.
  • Chore: Refreshed package dependencies for PR tools, including @sap-ai-sdk, @octokit plugins, zod, minimatch, ESLint, Prettier, TypeScript, and related utilities to their latest patch versions.

Model: o4-mini-2025-04-16 | Prompt Tokens: 2669 | Completion Tokens: 728 | Diff Range: 64fdef0...7bd5013

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

I’m happy to provide an AI-supported review of your code. These ideas are educated suggestions, not hard rules, so choose what aligns with your goals. You remain in control—AI is here to offer friendly guidance.

Model: o4-mini-2025-04-16 | Prompt Tokens: 2108 | Completion Tokens: 2558 | Diff Range: 64fdef0...7bd5013

Comment thread pr-review/package.json
Comment on lines 17 to 31
"@actions/core": "3.0.1",
"@actions/github": "9.1.1",
"@octokit/action": "7.0.2",
"@octokit/plugin-retry": "8.1.0",
"@octokit/plugin-throttling": "11.0.3",
"@octokit/plugin-retry": "8.1.1",
"@octokit/plugin-throttling": "11.0.5",
"@octokit/webhooks": "13.9.1",
"@sap-ai-sdk/ai-api": "2.10.0",
"@sap-ai-sdk/orchestration": "2.10.0",
"@sap-ai-sdk/ai-api": "2.15.0",
"@sap-ai-sdk/orchestration": "2.15.0",
"axios": "1.16.1",
"minimatch": "10.2.5",
"minimatch": "10.2.6",
"mollitia": "0.2.0",
"octokit": "5.0.5",
"parse-diff": "0.12.0",
"zod": "4.4.3"
"zod": "4.6.5"
},

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Consider consolidating shared dependencies between pr-review and pr-summary into a root-level workspace or monorepo. This reduces duplication and ensures consistency across projects. For example, in your root package.json:

{
  "name": "my-github-actions",
  "private": true,
  "workspaces": [
    "pr-review",
    "pr-summary"
  ],
  "dependencies": {
    // shared deps here
  }
}

Then remove these common dependencies from each sub-package to streamline upgrades and maintenance.

Comment thread pr-review/package.json
Comment on lines 25 to +30
"axios": "1.16.1",
"minimatch": "10.2.5",
"minimatch": "10.2.6",
"mollitia": "0.2.0",
"octokit": "5.0.5",
"parse-diff": "0.12.0",
"zod": "4.4.3"
"zod": "4.6.5"

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Switch to caret (^) version ranges instead of pinning exact versions. This allows non-breaking minor and patch updates automatically and keeps your dependencies fresher. For example:

-  "axios": "1.16.1",
+  "axios": "^1.16.1",
-  "zod": "4.6.5",
+  "zod": "^4.6.5",

Apply this consistently across both dependencies and devDependencies.

Comment thread pr-review/package.json
Comment on lines 17 to 45
"@actions/core": "3.0.1",
"@actions/github": "9.1.1",
"@octokit/action": "7.0.2",
"@octokit/plugin-retry": "8.1.0",
"@octokit/plugin-throttling": "11.0.3",
"@octokit/plugin-retry": "8.1.1",
"@octokit/plugin-throttling": "11.0.5",
"@octokit/webhooks": "13.9.1",
"@sap-ai-sdk/ai-api": "2.10.0",
"@sap-ai-sdk/orchestration": "2.10.0",
"@sap-ai-sdk/ai-api": "2.15.0",
"@sap-ai-sdk/orchestration": "2.15.0",
"axios": "1.16.1",
"minimatch": "10.2.5",
"minimatch": "10.2.6",
"mollitia": "0.2.0",
"octokit": "5.0.5",
"parse-diff": "0.12.0",
"zod": "4.4.3"
"zod": "4.6.5"
},
"devDependencies": {
"@eslint/js": "9.39.4",
"@types/node": "24.12.4",
"@vercel/ncc": "0.38.4",
"eslint": "9.39.4",
"@eslint/js": "9.39.5",
"@types/node": "24.13.5",
"@vercel/ncc": "0.45.0",
"eslint": "9.39.5",
"eslint-plugin-import": "2.32.0",
"eslint-plugin-sonarjs": "4.0.3",
"eslint-plugin-sonarjs": "4.2.1",
"eslint-plugin-unicorn": "64.0.0",
"prettier": "3.8.3",
"tsx": "4.22.3",
"prettier": "3.9.8",
"tsx": "4.23.13",
"typescript": "6.0.3",
"typescript-eslint": "8.59.4",
"yaml": "2.9.0"
"typescript-eslint": "8.70.0",
"yaml": "2.9.1"
}

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Alphabetize your dependencies and devDependencies for improved readability and easier diff reviews. For example:

"dependencies": {
  "@actions/core": "^3.0.1",
  "@actions/github": "^9.1.1",
  "@octokit/action": "^7.0.2",
  "@octokit/plugin-retry": "^8.1.1",
  // … rest sorted alphabetically
},
"devDependencies": {
  "@eslint/js": "^9.39.5",
  "@types/node": "^24.13.5",
  "@vercel/ncc": "^0.45.0",
  // … rest sorted
}

Comment thread pr-summary/package.json
Comment on lines 27 to 28
"octokit": "5.0.5",
"parse-diff": "0.12.0",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Consider removing the outdated standalone octokit package (v5.0.5) if you're only using the scoped @octokit/* packages for your GitHub Actions. This avoids confusion and reduces bundle size. If you need a client, use:

-  "octokit": "5.0.5",
+  // removed in favor of @actions/github or @octokit/action

Comment thread pr-summary/package.json
"typescript-eslint": "8.70.0",
"yaml": "2.9.1"
}
}

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

You can introduce an engines field to enforce a minimum Node.js version for consistency across CI and local environments. For example:

"engines": {
  "node": ">=18.0"
},

Comment thread pr-summary/package.json
Comment on lines -39 to +43
"prettier": "3.8.3",
"tsx": "4.22.3",
"prettier": "3.9.8",
"tsx": "4.23.13",
"typescript": "6.0.3",
"typescript-eslint": "8.59.4",
"yaml": "2.9.0"
"typescript-eslint": "8.70.0",
"yaml": "2.9.1"

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Apply caret version ranges (^) for your dependencies so that patch and minor updates are picked up automatically. For example:

-  "prettier": "3.9.8",
+  "prettier": "^3.9.8",
-  "typescript-eslint": "8.70.0",
+  "typescript-eslint": "^8.70.0",

@renovate
renovate Bot force-pushed the renovate/non-major-dependencies branch from 7bd5013 to 818d010 Compare September 18, 2026 16:04
@github-actions

Copy link
Copy Markdown

Upgrades CI workflows and internal libraries to their latest patch releases, improving build stability and ensuring compatibility with current Node and GitHub Actions versions.

Walkthrough

  • Chore: Bumped actions/checkout (v7.0.0 → v7.0.1) and actions/setup-node (v6.4.0 → v6.5.0) in build and code-quality workflows for more reliable builds.
  • Chore: Updated core libraries in both pr-summary and pr-review packages (Octokit, SAP AI SDK, Zod, Minimatch) to address bug fixes and performance improvements.
  • Chore: Refreshed devDependencies (ESLint, TypeScript, Prettier, ncc, TSX, YAML plugins) to keep the toolchain current.

Model: o4-mini-2025-04-16 | Prompt Tokens: 2669 | Completion Tokens: 502 | Diff Range: 7bd5013...818d010

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Enjoy this supportive code review powered by AI. Treat its suggestions as ideas rather than certainties, and apply what fits your needs. You’re in charge—AI’s role is to help you shine.

Model: o4-mini-2025-04-16 | Prompt Tokens: 2108 | Completion Tokens: 4202 | Diff Range: 7bd5013...818d010

Comment thread pr-review/package.json
Comment on lines 17 to 31
"@actions/core": "3.0.1",
"@actions/github": "9.1.1",
"@octokit/action": "7.0.2",
"@octokit/plugin-retry": "8.1.0",
"@octokit/plugin-throttling": "11.0.3",
"@octokit/plugin-retry": "8.1.1",
"@octokit/plugin-throttling": "11.0.5",
"@octokit/webhooks": "13.9.1",
"@sap-ai-sdk/ai-api": "2.10.0",
"@sap-ai-sdk/orchestration": "2.10.0",
"@sap-ai-sdk/ai-api": "2.16.0",
"@sap-ai-sdk/orchestration": "2.16.0",
"axios": "1.16.1",
"minimatch": "10.2.5",
"minimatch": "10.2.6",
"mollitia": "0.2.0",
"octokit": "5.0.5",
"parse-diff": "0.12.0",
"zod": "4.4.3"
"zod": "4.6.5"
},

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Suggest using caret (^) version ranges instead of pinning exact versions. This allows automatic patch and minor updates while preventing breaking major changes.

For example:

"dependencies": {
  "@actions/core": "^3.0.1",
  "@actions/github": "^9.1.1",
  // ...
}

Comment thread pr-review/package.json
Comment on lines 17 to 46
"@actions/core": "3.0.1",
"@actions/github": "9.1.1",
"@octokit/action": "7.0.2",
"@octokit/plugin-retry": "8.1.0",
"@octokit/plugin-throttling": "11.0.3",
"@octokit/plugin-retry": "8.1.1",
"@octokit/plugin-throttling": "11.0.5",
"@octokit/webhooks": "13.9.1",
"@sap-ai-sdk/ai-api": "2.10.0",
"@sap-ai-sdk/orchestration": "2.10.0",
"@sap-ai-sdk/ai-api": "2.16.0",
"@sap-ai-sdk/orchestration": "2.16.0",
"axios": "1.16.1",
"minimatch": "10.2.5",
"minimatch": "10.2.6",
"mollitia": "0.2.0",
"octokit": "5.0.5",
"parse-diff": "0.12.0",
"zod": "4.4.3"
"zod": "4.6.5"
},
"devDependencies": {
"@eslint/js": "9.39.4",
"@types/node": "24.12.4",
"@vercel/ncc": "0.38.4",
"eslint": "9.39.4",
"@eslint/js": "9.39.5",
"@types/node": "24.13.5",
"@vercel/ncc": "0.45.0",
"eslint": "9.39.5",
"eslint-plugin-import": "2.32.0",
"eslint-plugin-sonarjs": "4.0.3",
"eslint-plugin-sonarjs": "4.2.1",
"eslint-plugin-unicorn": "64.0.0",
"prettier": "3.8.3",
"tsx": "4.22.3",
"prettier": "3.9.8",
"tsx": "4.23.13",
"typescript": "6.0.3",
"typescript-eslint": "8.59.4",
"yaml": "2.9.0"
"typescript-eslint": "8.70.0",
"yaml": "2.9.1"
}
}

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

You have identical dependency and devDependency updates in both pr-review and pr-summary package.json files. Consider hoisting shared dependencies to a root-level package.json with workspace support to avoid duplication and simplify version management.

For example, in the root package.json:

{
  "private": true,
  "workspaces": ["pr-review", "pr-summary"],
  "dependencies": {
    "@sap-ai-sdk/ai-api": "2.16.0",
    "@sap-ai-sdk/orchestration": "2.16.0",
    // ... shared deps
  }
}

Comment thread pr-review/package.json
Comment on lines 17 to 31
"@actions/core": "3.0.1",
"@actions/github": "9.1.1",
"@octokit/action": "7.0.2",
"@octokit/plugin-retry": "8.1.0",
"@octokit/plugin-throttling": "11.0.3",
"@octokit/plugin-retry": "8.1.1",
"@octokit/plugin-throttling": "11.0.5",
"@octokit/webhooks": "13.9.1",
"@sap-ai-sdk/ai-api": "2.10.0",
"@sap-ai-sdk/orchestration": "2.10.0",
"@sap-ai-sdk/ai-api": "2.16.0",
"@sap-ai-sdk/orchestration": "2.16.0",
"axios": "1.16.1",
"minimatch": "10.2.5",
"minimatch": "10.2.6",
"mollitia": "0.2.0",
"octokit": "5.0.5",
"parse-diff": "0.12.0",
"zod": "4.4.3"
"zod": "4.6.5"
},

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Alphabetize your dependencies and devDependencies entries to improve readability and maintainability. This makes it easier to locate packages and enforce consistency.

Example sorted dependencies:

"dependencies": {
  "@actions/core": "3.0.1",
  "@actions/github": "9.1.1",
  "@octokit/plugin-retry": "8.1.1",
  // ...
}

Comment thread pr-review/package.json
Comment on lines 28 to 29
"octokit": "5.0.5",
"parse-diff": "0.12.0",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

The octokit package at version 5.0.5 appears redundant since you're already using @octokit/webhooks, @actions/github, and the retry/throttling plugins. If you’re not directly invoking the old Octokit constructor, consider removing it to reduce bundle size.

- "octokit": "5.0.5",

Comment thread pr-review/package.json
@@ -17,30 +17,30 @@
"@actions/core": "3.0.1",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Add an engines field to enforce the Node.js version required by your action. This helps users install a compatible runtime and catches mismatches early.

Example:

"engines": {
  "node": ">=16.14.0"
}

Comment thread pr-summary/package.json
Comment on lines 16 to 30
"dependencies": {
"@actions/core": "3.0.1",
"@actions/github": "9.1.1",
"@octokit/plugin-retry": "8.1.0",
"@octokit/plugin-throttling": "11.0.3",
"@octokit/plugin-retry": "8.1.1",
"@octokit/plugin-throttling": "11.0.5",
"@octokit/webhooks": "13.9.1",
"@sap-ai-sdk/ai-api": "2.10.0",
"@sap-ai-sdk/orchestration": "2.10.0",
"@sap-ai-sdk/ai-api": "2.16.0",
"@sap-ai-sdk/orchestration": "2.16.0",
"axios": "1.16.1",
"minimatch": "10.2.5",
"minimatch": "10.2.6",
"mollitia": "0.2.0",
"octokit": "5.0.5",
"parse-diff": "0.12.0",
"zod": "4.4.3"
"zod": "4.6.5"
},

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Suggest using caret (^) version ranges instead of pinning exact versions. This allows automatic patch and minor updates while preventing breaking major changes.

For example:

"dependencies": {
  "@actions/core": "^3.0.1",
  "@actions/github": "^9.1.1",
  // ...
}

Comment thread pr-summary/package.json
Comment on lines 16 to 30
"dependencies": {
"@actions/core": "3.0.1",
"@actions/github": "9.1.1",
"@octokit/plugin-retry": "8.1.0",
"@octokit/plugin-throttling": "11.0.3",
"@octokit/plugin-retry": "8.1.1",
"@octokit/plugin-throttling": "11.0.5",
"@octokit/webhooks": "13.9.1",
"@sap-ai-sdk/ai-api": "2.10.0",
"@sap-ai-sdk/orchestration": "2.10.0",
"@sap-ai-sdk/ai-api": "2.16.0",
"@sap-ai-sdk/orchestration": "2.16.0",
"axios": "1.16.1",
"minimatch": "10.2.5",
"minimatch": "10.2.6",
"mollitia": "0.2.0",
"octokit": "5.0.5",
"parse-diff": "0.12.0",
"zod": "4.4.3"
"zod": "4.6.5"
},

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Alphabetize your dependencies and devDependencies entries to improve readability and maintainability. This makes it easier to locate packages and enforce consistency.

Example sorted dependencies:

"dependencies": {
  "@actions/core": "3.0.1",
  "@actions/github": "9.1.1",
  "@octokit/plugin-retry": "8.1.1",
  // ...
}

Comment thread pr-summary/package.json
Comment on lines 16 to 45
"dependencies": {
"@actions/core": "3.0.1",
"@actions/github": "9.1.1",
"@octokit/plugin-retry": "8.1.0",
"@octokit/plugin-throttling": "11.0.3",
"@octokit/plugin-retry": "8.1.1",
"@octokit/plugin-throttling": "11.0.5",
"@octokit/webhooks": "13.9.1",
"@sap-ai-sdk/ai-api": "2.10.0",
"@sap-ai-sdk/orchestration": "2.10.0",
"@sap-ai-sdk/ai-api": "2.16.0",
"@sap-ai-sdk/orchestration": "2.16.0",
"axios": "1.16.1",
"minimatch": "10.2.5",
"minimatch": "10.2.6",
"mollitia": "0.2.0",
"octokit": "5.0.5",
"parse-diff": "0.12.0",
"zod": "4.4.3"
"zod": "4.6.5"
},
"devDependencies": {
"@eslint/js": "9.39.4",
"@types/node": "24.12.4",
"@vercel/ncc": "0.38.4",
"eslint": "9.39.4",
"@eslint/js": "9.39.5",
"@types/node": "24.13.5",
"@vercel/ncc": "0.45.0",
"eslint": "9.39.5",
"eslint-plugin-import": "2.32.0",
"eslint-plugin-sonarjs": "4.0.3",
"eslint-plugin-sonarjs": "4.2.1",
"eslint-plugin-unicorn": "64.0.0",
"prettier": "3.8.3",
"tsx": "4.22.3",
"prettier": "3.9.8",
"tsx": "4.23.13",
"typescript": "6.0.3",
"typescript-eslint": "8.59.4",
"yaml": "2.9.0"
"typescript-eslint": "8.70.0",
"yaml": "2.9.1"
}
}

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

As with the other module, these dependency updates are duplicated. Consider hoisting shared dependencies into a root-level package.json with workspaces to keep versions in sync and reduce maintenance.

{
  "private": true,
  "workspaces": ["pr-review", "pr-summary"],
  // shared deps here
}

@renovate
renovate Bot force-pushed the renovate/non-major-dependencies branch from 818d010 to d65a218 Compare September 19, 2026 00:35
@github-actions

Copy link
Copy Markdown

This update modernizes the CI pipelines and internal libraries by upgrading GitHub Actions (checkout and setup-node) to their latest patch releases and bumping key npm dependencies across both pr-review and pr-summary packages. These dependency upgrades include retry/throttling plugins, the SAP AI SDK, linting tools, and TypeScript support, ensuring improved performance, security fixes, and compatibility without altering user-facing behavior.

Walkthrough

  • Chore: Upgraded GitHub Actions checkout to v7.0.1 and setup-node to v6.5.0 in build and code-quality workflows
  • Chore: Bumped core dependencies (e.g., @octokit, SAP AI SDK, axios, zod) for bug fixes and performance
  • Chore: Updated devDependencies (ESLint, TypeScript, Prettier, etc.) to latest patch releases for consistency and better tooling support

Model: o4-mini-2025-04-16 | Prompt Tokens: 2669 | Completion Tokens: 527 | Diff Range: 818d010...d65a218

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Thank you for sharing your code! AI offers friendly suggestions to consider rather than absolute rules. Feel free to pick what aligns with your vision, trust your experience, and make the final call. AI is here to support your expertise.

Model: o4-mini-2025-04-16 | Prompt Tokens: 2108 | Completion Tokens: 3350 | Diff Range: 818d010...d65a218

Comment thread pr-review/package.json
Comment on lines -20 to +21
"@octokit/plugin-retry": "8.1.0",
"@octokit/plugin-throttling": "11.0.3",
"@octokit/plugin-retry": "8.1.1",
"@octokit/plugin-throttling": "11.0.5",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Consider switching to caret version ranges for patch-level flexibility to reduce the need for frequent PRs on minor fixes. For example:

"@octokit/plugin-retry": "^8.1.1",
"@octokit/plugin-throttling": "^11.0.5"

Comment thread pr-summary/package.json
Comment on lines -19 to +20
"@octokit/plugin-retry": "8.1.0",
"@octokit/plugin-throttling": "11.0.3",
"@octokit/plugin-retry": "8.1.1",
"@octokit/plugin-throttling": "11.0.5",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

The same Octokit plugin upgrades are applied here. To avoid duplication and drift, consider consolidating shared dependencies at the workspace root. For example in your root package.json:

{
  "workspaces": ["pr-review", "pr-summary"]
}

Comment thread pr-review/package.json
Comment on lines -33 to +36
"@eslint/js": "9.39.4",
"@types/node": "24.12.4",
"@vercel/ncc": "0.38.4",
"eslint": "9.39.4",
"@eslint/js": "9.39.5",
"@types/node": "24.13.6",
"@vercel/ncc": "0.45.0",
"eslint": "9.39.5",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

After bumping ESLint and TypeScript, ensure your ESLint configuration is updated to use the new parser. For instance, in .eslintrc.json:

{
  "parser": "@typescript-eslint/parser",
  "parserOptions": {
    "project": "./tsconfig.json"
  }
}

Comment thread pr-summary/package.json
Comment on lines -39 to +43
"prettier": "3.8.3",
"tsx": "4.22.3",
"prettier": "3.9.8",
"tsx": "4.23.13",
"typescript": "6.0.3",
"typescript-eslint": "8.59.4",
"yaml": "2.9.0"
"typescript-eslint": "8.70.0",
"yaml": "2.9.1"

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Don't forget to regenerate and commit your lockfile (package-lock.json or yarn.lock) after updating dependencies. Run:

npm install
# or in CI
npm ci

@github-actions

Copy link
Copy Markdown

This update refreshes CI workflows to use the latest GitHub Actions versions and bumps a range of internal and development dependencies across the pr-review and pr-summary packages. There are no user-facing feature changes, but builds now benefit from improved stability, security patches, and tooling enhancements.

Walkthrough

  • Chore: Upgraded actions/checkout to v7.0.1 and actions/setup-node to v6.5.0 in build and code-quality workflows.
  • Chore: Bumped Octokit plugins (plugin-retry, plugin-throttling) and SAP AI SDK packages to latest patch releases for reliability.
  • Chore: Updated core libs (zod, minimatch) and dev tooling (ESLint, TypeScript, Prettier, ncc, tsx, YAML) to current versions.

Model: o4-mini-2025-04-16 | Prompt Tokens: 2669 | Completion Tokens: 1026 | Diff Range: d65a218...2861ea6

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Here’s a friendly code review with AI support to spark ideas and catch potential enhancements. Since not every suggestion is a certainty, pick the insights that resonate with you. You’re in the driver’s seat, guiding the final decisions. AI simply offers extra perspective.

Model: o4-mini-2025-04-16 | Prompt Tokens: 2108 | Completion Tokens: 3046 | Diff Range: d65a218...2861ea6

Comment thread pr-review/package.json
Comment on lines -43 to +44
"typescript-eslint": "8.59.4",
"yaml": "2.9.0"
"typescript-eslint": "8.70.0",
"yaml": "2.9.1"

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

It looks like you’re using a devDependency called typescript-eslint, but there is no official package by that exact name on npm. You probably meant the ESLint plugin and parser from the @typescript-eslint scope. For example:

{
  "devDependencies": {
    "@typescript-eslint/eslint-plugin": "^8.70.0",
    "@typescript-eslint/parser": "^8.70.0",
    // …other devDependencies
  }
}

Comment thread pr-summary/package.json
Comment on lines -42 to +43
"typescript-eslint": "8.59.4",
"yaml": "2.9.0"
"typescript-eslint": "8.70.0",
"yaml": "2.9.1"

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Similar to the comment above, typescript-eslint is not a real package on npm. You should replace it with the correct scoped packages, for example:

{
  "devDependencies": {
    "@typescript-eslint/eslint-plugin": "^8.70.0",
    "@typescript-eslint/parser": "^8.70.0",
    // …other devDependencies
  }
}

Comment thread pr-review/package.json
Comment on lines 17 to -30
"@actions/core": "3.0.1",
"@actions/github": "9.1.1",
"@octokit/action": "7.0.2",
"@octokit/plugin-retry": "8.1.0",
"@octokit/plugin-throttling": "11.0.3",
"@octokit/plugin-retry": "8.1.1",
"@octokit/plugin-throttling": "11.0.5",
"@octokit/webhooks": "13.9.1",
"@sap-ai-sdk/ai-api": "2.10.0",
"@sap-ai-sdk/orchestration": "2.10.0",
"@sap-ai-sdk/ai-api": "2.16.0",
"@sap-ai-sdk/orchestration": "2.16.0",
"axios": "1.16.1",
"minimatch": "10.2.5",
"minimatch": "10.2.6",
"mollitia": "0.2.0",
"octokit": "5.0.5",
"parse-diff": "0.12.0",
"zod": "4.4.3"

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

You’re pinning almost every dependency to an exact version. While this guarantees reproducibility, it also prevents patch updates (security fixes, small bug fixes) from being automatically pulled in. Consider using caret ranges to allow non-breaking updates, for example:

- "@octokit/plugin-retry": "8.1.1",
+ "@octokit/plugin-retry": "^8.1.1",
- "zod": "4.6.5"
+ "zod": "^4.6.5"

This way, running npm update will safely pull in any 4.x.x or 8.x.x patches without manual version bumps.

Comment thread pr-summary/package.json
Comment on lines 16 to -29
"dependencies": {
"@actions/core": "3.0.1",
"@actions/github": "9.1.1",
"@octokit/plugin-retry": "8.1.0",
"@octokit/plugin-throttling": "11.0.3",
"@octokit/plugin-retry": "8.1.1",
"@octokit/plugin-throttling": "11.0.5",
"@octokit/webhooks": "13.9.1",
"@sap-ai-sdk/ai-api": "2.10.0",
"@sap-ai-sdk/orchestration": "2.10.0",
"@sap-ai-sdk/ai-api": "2.16.0",
"@sap-ai-sdk/orchestration": "2.16.0",
"axios": "1.16.1",
"minimatch": "10.2.5",
"minimatch": "10.2.6",
"mollitia": "0.2.0",
"octokit": "5.0.5",
"parse-diff": "0.12.0",
"zod": "4.4.3"

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

As above, you might want to switch from exact version pins to semver ranges for better maintainability. For example:

- "minimatch": "10.2.6",
+ "minimatch": "^10.2.6",
- "prettier": "3.9.8",
+ "prettier": "^3.9.8",

This helps your project automatically pick up patch releases (security or bug fixes) while avoiding unintended major upgrades.

Comment thread pr-review/package.json
Comment on lines 17 to 45
"@actions/core": "3.0.1",
"@actions/github": "9.1.1",
"@octokit/action": "7.0.2",
"@octokit/plugin-retry": "8.1.0",
"@octokit/plugin-throttling": "11.0.3",
"@octokit/plugin-retry": "8.1.1",
"@octokit/plugin-throttling": "11.0.5",
"@octokit/webhooks": "13.9.1",
"@sap-ai-sdk/ai-api": "2.10.0",
"@sap-ai-sdk/orchestration": "2.10.0",
"@sap-ai-sdk/ai-api": "2.16.0",
"@sap-ai-sdk/orchestration": "2.16.0",
"axios": "1.16.1",
"minimatch": "10.2.5",
"minimatch": "10.2.6",
"mollitia": "0.2.0",
"octokit": "5.0.5",
"parse-diff": "0.12.0",
"zod": "4.4.3"
"zod": "4.6.5"
},
"devDependencies": {
"@eslint/js": "9.39.4",
"@types/node": "24.12.4",
"@vercel/ncc": "0.38.4",
"eslint": "9.39.4",
"@eslint/js": "9.39.5",
"@types/node": "24.13.6",
"@vercel/ncc": "0.45.0",
"eslint": "9.39.5",
"eslint-plugin-import": "2.32.0",
"eslint-plugin-sonarjs": "4.0.3",
"eslint-plugin-sonarjs": "4.2.1",
"eslint-plugin-unicorn": "64.0.0",
"prettier": "3.8.3",
"tsx": "4.22.3",
"prettier": "3.9.8",
"tsx": "4.23.15",
"typescript": "6.0.3",
"typescript-eslint": "8.59.4",
"yaml": "2.9.0"
"typescript-eslint": "8.70.0",
"yaml": "2.9.1"
}

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

I see both pr-review and pr-summary share almost identical dependencies and devDependencies. To avoid duplication and simplify version bumps across both packages, consider converting the repo into a monorepo using npm or Yarn workspaces. For example, add a root package.json:

{
  "private": true,
  "workspaces": [
    "pr-review",
    "pr-summary"
  ],
  "devDependencies": {
    // shared scripts or tooling here
  }
}

Then move common dependencies into each workspace’s package.json only when strictly necessary, keeping the shared ones at the root level. This reduces overhead when updating versions and keeps consistency across your actions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants