Bump production npm/yarn dependencies to latest minor/patch versions

[donny-devops]

@copilot

[gemini-code-assist]

Caution

The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased.

[codacy-production]

Not up to standards ⛔

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.}

[deepsource-io]

DeepSource Code Review

We reviewed changes in 6f9abb0...1da142e on this pull request. Below is the summary for the review, and you can see the individual issues we found as inline review comments.

See full review on DeepSource ↗

PR Report Card

Overall Grade

Security   Reliability   Complexity   Hygiene

Code Review Summary

Analyzer	Status	Updated (UTC)	Details
Docker		Aug 22, 2026 6:19a.m.	Review ↗
JavaScript		Aug 22, 2026 6:19a.m.	Review ↗
Python		Aug 22, 2026 6:19a.m.	Review ↗
Secrets		Aug 22, 2026 6:19a.m.	Review ↗

---

Important

AI Review is run only on demand for your team. We're only showing results of static analysis review right now. To trigger AI Review, comment @deepsourcebot review on this thread.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	typescript@​5.9.3 ⏵ 7.0.2			-1		+10
	eslint@​8.57.1 ⏵ 10.7.0	+1			+47

View full report

[amazon-q-developer]

Summary

This PR contains critical issues that block merge. While the PR title indicates "minor/patch versions," the changes include major version updates that introduce breaking changes:

• ESLint: v8.57.0 → v10.7.0 (major version jump)
• TypeScript: v5.4.5 → v7.0.2 (major version jump)

Major version updates typically include breaking changes that can cause:

• Compilation failures
• Linting configuration incompatibilities
• Breaking changes requiring code modifications
• Plugin incompatibilities

Action Required: Either update the PR to only include minor/patch updates as stated, or if major updates are intentional, rename the PR appropriately, ensure all tests pass, and document any breaking changes or required migrations.

---

You can now have the agent implement changes and create commits directly on your pull request's source branch. Simply comment with /q followed by your request in natural language to ask the agent to make changes.

[qodo-code-review]

PR Summary by Qodo

Add GitHub issue templates and bump ESLint/TypeScript dev toolchain

⚙️ Configuration changes ✨ Enhancement 🕐 20-40 Minutes

AI Description

• Add GitHub issue templates to standardize bug reports and feature requests.
• Bump ESLint to v10 and TypeScript to v7 to modernize the dev toolchain.
• Refresh npm lockfile to reflect updated transitive dependencies and metadata.

Diagram

graph TD
  A["Dev/CI"] --> B["package.json"] --> C["package-lock.json"] --> D["node_modules"]
  D --> E["ESLint 10"]
  D --> F["TypeScript 7"]
  G["GitHub Issues"] --> H["Issue templates"]

Loading

High-Level Assessment

The following are alternative approaches to this PR:

1. Keep TypeScript at v5.x until linters/tooling support v7

• ➕ Avoids potential peer-dependency incompatibilities with @typescript-eslint/* and ts-jest
• ➕ Reduces risk of CI/install failures caused by strict peer deps
• ➖ Delays adoption of TypeScript 7 features/fixes
• ➖ Requires follow-up PR later for the TS7 upgrade

2. Upgrade TypeScript ecosystem together (typescript-eslint/ts-jest) in same PR

• ➕ Keeps TypeScript and lint/test tooling compatible in one step
• ➕ Reduces time spent debugging mismatched compiler/parser versions
• ➖ Larger, riskier PR with more moving parts
• ➖ May require code/config updates to satisfy new tooling rules/behavior

3. Split: ESLint 10 PR, then TypeScript 7 PR

• ➕ Simplifies rollback and isolates failures to one major upgrade
• ➕ Makes review and troubleshooting more focused
• ➖ More PR overhead
• ➖ Lockfile churn twice

Recommendation: Proceed with the issue templates as-is, but double-check the TypeScript 7 upgrade against the current @typescript-eslint/* versions: the lockfile shows peerDependencies that cap TypeScript at <6.1.0, which is likely to cause npm peer-dep warnings or failures depending on install settings. If the repo enforces strict peer deps, either (a) upgrade the TypeScript-related tooling to versions compatible with TS7 in this PR, or (b) keep TypeScript on the highest supported 5.x/6.0.x range and follow up once the ecosystem is aligned. Also verify Node engine compatibility: ESLint 10’s dependency graph indicates a much newer Node requirement than ESLint 8.

Files changed (5) +811 / -472

Other (5) +811 / -472

bug_report.mdAdd bug report issue template +38/-0

Add bug report issue template

• Introduces a standardized GitHub bug report template with sections for reproduction steps, expected behavior, and environment details.

.github/ISSUE_TEMPLATE/bug_report.md

custom.mdAdd placeholder custom issue template +10/-0

Add placeholder custom issue template

• Adds a minimal custom issue template scaffold for future use.

.github/ISSUE_TEMPLATE/custom.md

feature_request.mdAdd feature request issue template +20/-0

Add feature request issue template

• Introduces a standardized GitHub feature request template covering problem statement, desired solution, and alternatives.

.github/ISSUE_TEMPLATE/feature_request.md

package-lock.jsonRefresh lockfile for ESLint 10 / TypeScript 7 upgrades +741/-470

Refresh lockfile for ESLint 10 / TypeScript 7 upgrades

• Updates the resolved dependency tree to match ESLint ^10.7.0 and TypeScript ^7.0.2, including large transitive dependency changes and new optional TypeScript platform packages.

package-lock.json

package.jsonBump ESLint to 10.7.0 and TypeScript to 7.0.2 +2/-2

Bump ESLint to 10.7.0 and TypeScript to 7.0.2

• Updates direct devDependencies to ESLint ^10.7.0 and TypeScript ^7.0.2 to modernize linting and compilation tooling.

package.json

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: b190e839a9

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[Copilot]

Pull request overview

Updates the repository’s Node/TypeScript tooling dependencies (notably ESLint and TypeScript) and refreshes the npm lockfile; additionally, it introduces GitHub issue templates under .github/ISSUE_TEMPLATE.

Changes:

• Bump dev toolchain dependencies in package.json (ESLint 8 → 10, TypeScript 5 → 7).
• Update package-lock.json to reflect the new dependency graph for the upgraded toolchain.
• Add GitHub Issue Templates for bug reports, feature requests, and a custom template.

Reviewed changes

Copilot reviewed 4 out of 5 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
package.json	Bumps ESLint and TypeScript versions (tooling/devDependencies).
package-lock.json	Regenerates lockfile to match updated dependency versions and transitive tree.
.github/ISSUE_TEMPLATE/feature_request.md	Adds a feature request issue template.
.github/ISSUE_TEMPLATE/custom.md	Adds a custom issue template (currently needs non-placeholder metadata/body).
.github/ISSUE_TEMPLATE/bug_report.md	Adds a bug report issue template.

Suppressed comments (1)

.github/ISSUE_TEMPLATE/custom.md:11

• This template’s body is empty, so users selecting it will get a blank issue form (lowering report quality). Consider adding at least a few prompts (summary, expected/actual, reproduction, etc.).

---

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (1) 📘 Rule violations (0) 📜 Skill insights (0)

Context used

✅ Compliance rules (platform): 82 rules

1. TypeScript peer mismatch 🐞 Bug ☼ Reliability

Description

This PR bumps TypeScript to ^7.0.2, but the installed @typescript-eslint/parser declares a
peerDependency of TypeScript <6.1.0 and ts-jest declares TypeScript <7, so the repo now has an
explicit peer-dependency incompatibility. This can break installs under strict peer-deps and runs
ESLint/Jest outside their declared supported TypeScript range.

Code

package.json[51]

+    "typescript": "^7.0.2"

Relevance

●● Moderate

Mixed history: fixed peer-dep conflicts before (PR#90) but still merged TS 7 bump (PR#110).

PR-#90
PR-#110

ⓘ Recommendations generated based on similar findings in past PRs

Evidence

The repo now depends on TypeScript 7, while the lockfile shows both the ESLint TS parser and Jest TS
transformer explicitly restricting supported TypeScript versions to ranges that exclude 7.x; since
the scripts run eslint/jest, this incompatibility directly impacts CI/dev workflows.

package.json[6-18]
package.json[35-52]
package-lock.json[1889-1912]
package-lock.json[7093-7124]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
TypeScript was upgraded to v7, but linting and testing dependencies declare peer ranges that exclude TypeScript 7, creating a peer-dependency conflict and unsupported tooling behavior.

## Issue Context
- `@typescript-eslint/parser` peerDependency requires `typescript: ">=4.8.4 <6.1.0"`.
- `ts-jest` peerDependency requires `typescript: ">=4.3 <7"`.
- The repo runs ESLint/Jest via package scripts.

## Fix Focus Areas
- package.json[35-52]
- package-lock.json[1889-1912]
- package-lock.json[7093-7124]

## What to change
- Either:
 - Downgrade/pin `typescript` to a version satisfying **all** current peer ranges (e.g., <6.1.0 and <7), OR
 - Upgrade `@typescript-eslint/*` and `ts-jest` to versions that explicitly support TypeScript 7, then update the lockfile accordingly.
- After adjusting versions, run `npm ci` + `npm run lint` + `npm test` to ensure the toolchain works end-to-end.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

_{To customize comments, go to the Qodo configuration screen, or learn more in the docs.}