chore(deps): update dependency @types/node to v24

[red-hat-konflux]

This PR contains the following updates:

Package	Change	Age	Confidence
@types/node (source)	^22.10.2 → ^24.0.0

---

Warning

Some dependencies could not be looked up. Check the warning logs for more information.

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

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

---

To execute skipped test pipelines write comment /ok-to-test.

---

Documentation

Find out how to configure dependency updates in MintMaker documentation or see all available configuration options in Renovate documentation.

[coderabbitai]

Walkthrough

Updated the @types/node development dependency version from ^22.10.2 to ^24.0.0 in the package manifest, affecting TypeScript type definitions used for Node.js development and type-checking.

Changes

Cohort / File(s)	Summary
Dependency Update mcp/package.json	Bumped @types/node version from ^22.10.2 to ^24.0.0, updating Node.js TypeScript type definitions.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly describes the main change: updating the @types/node dependency from v22 to v24. It is concise, specific, and directly reflects the changeset.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description check	✅ Passed	The PR description clearly relates to the changeset, detailing the @types/node dependency update from ^22.10.2 to ^24.0.0 with relevant metadata.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch konflux/mintmaker/master/node-24.x

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

🧹 Nitpick comments (1)

mcp/package.json (1)

38-38: Align @types/node version with minimum supported runtime (Line 38).

@types/node@^24.0.0 declares support for Node 24 APIs at compile-time, but engines.node specifies >=20.0.0. While the code currently only uses APIs available in Node 20+ (e.g., process.env, process.uptime(), Buffer.from()), this mismatch can invite future incompatibilities if newer code additions aren't carefully checked.

Consider pinning @types/node to match the minimum supported major version (e.g., @types/node@^20.0.0) or tightening engines.node to match the TypeScript library version.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@mcp/package.json` at line 38, Package.json currently depends on
"@types/node": "^24.0.0" which is higher than the declared runtime minimum in
engines.node (>=20.0.0); update the dependency to match the minimum supported
major Node version (for example change the "@types/node" entry from "^24.0.0" to
"^20.0.0") or alternatively tighten engines.node to the new minimum (e.g., set
engines.node to ">=24.0.0") so the declared TypeScript lib and runtime align;
modify the "@types/node" line in package.json (the dependency string
"@types/node": "^24.0.0") or adjust the engines.node field accordingly and run
npm/Yarn install to update lockfile.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@mcp/package.json`:
- Line 38: Package.json currently depends on "@types/node": "^24.0.0" which is
higher than the declared runtime minimum in engines.node (>=20.0.0); update the
dependency to match the minimum supported major Node version (for example change
the "@types/node" entry from "^24.0.0" to "^20.0.0") or alternatively tighten
engines.node to the new minimum (e.g., set engines.node to ">=24.0.0") so the
declared TypeScript lib and runtime align; modify the "@types/node" line in
package.json (the dependency string "@types/node": "^24.0.0") or adjust the
engines.node field accordingly and run npm/Yarn install to update lockfile.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: d4a4d1d3-09b2-48df-b0b6-fddb38876b32

📥 Commits

Reviewing files that changed from the base of the PR and between dcf6065 and 5c6684f.

⛔ Files ignored due to path filters (1)

• mcp/package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (1)

• mcp/package.json