chore(deps): bump typescript-eslint from 8.46.2 to 8.47.0 in /apps/frontend

[dependabot]

Bumps typescript-eslint from 8.46.2 to 8.47.0.

Release notes

Sourced from typescript-eslint's releases.

v8.47.0

8.47.0 (2025-11-17)

🚀 Features

• eslint-plugin: [no-unused-private-class-members] new extension rule (#10913)

❤️ Thank You

• Brad Zacher @​bradzacher

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

v8.46.4

8.46.4 (2025-11-10)

🩹 Fixes

• eslint-plugin: [no-deprecated] fix double-report on computed literal identifiers (#11006, #10958)
• eslint-plugin: handle override modifier in promise-function-async fixer (#11730)
• parser: error when both projectService and project are set (#11333)

❤️ Thank You

• Evgeny Stepanovych @​undsoft
• Kentaro Suzuki @​sushichan044
• Maria Solano @​MariaSolOs

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

v8.46.3

8.46.3 (2025-11-03)

🩹 Fixes

• eslint-plugin: [no-misused-promises] expand union type to retrieve target property (#11706)
• eslint-plugin: [no-duplicate-enum-values] support signed numbers (#11722, #11723)

❤️ Thank You

• Evgeny Stepanovych @​undsoft
• tao

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

Changelog

Sourced from typescript-eslint's changelog.

8.47.0 (2025-11-17)

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

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

8.46.4 (2025-11-10)

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

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

8.46.3 (2025-11-03)

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

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

Commits

• 28cf803 chore(release): publish 8.47.0
• 843f144 chore(release): publish 8.46.4
• 7c6944e chore: fix typos (#11744)
• d9f3497 chore(release): publish 8.46.3
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

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

[fingertips18]

@coderabbitai please confirm that this is good to merge and there are no breaking changes?

[coderabbitai]

Tip

For best results, initiate chat on the files or code changes.

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Check the package.json in apps/frontend for typescript-eslint
cat apps/frontend/package.json | jq '.dependencies["typescript-eslint"], .devDependencies["typescript-eslint"]'

# Find eslint configuration files in apps/frontend
fd -e json -e js -e cjs -e mjs -e yaml -e yml 'eslint' apps/frontend

# Check if there are any typescript-eslint rules configured
fd 'eslint.config' apps/frontend --exec cat {}

Length of output: 1239

---

@fingertips18: Yes, this is safe to merge with no breaking changes. Here's my analysis:

✅ Version Bump Analysis:

• This is a minor version bump (8.46.2 → 8.47.0), which follows semantic versioning and guarantees backward compatibility
• The changelog explicitly states: "This was a version bump only for typescript-eslint to align it with other projects, there were no code changes"

✅ Changes Included:

• v8.47.0: Adds a new optional rule no-unused-private-class-members - this is opt-in and won't affect your codebase unless explicitly enabled
• v8.46.4: Bug fixes for no-deprecated and promise-function-async rules
• v8.46.3: Bug fixes for no-misused-promises and no-duplicate-enum-values rules

✅ Configuration Safety:
Your project uses tseslint.configs.recommended, which is maintained to be stable across minor versions. The new rule is not part of the recommended config, so it won't introduce any new lint errors.

Recommendation: Safe to merge. The update includes only bug fixes and an optional new feature that won't impact your existing code.