[Snyk] Fix for 1 vulnerabilities

[posit-snyk-bot]

Snyk has created this PR to fix 1 vulnerabilities in the yarn dependencies of this project.

Snyk changed the following file(s):

• packages/eslint-config-custom/package.json

Note for zero-installs users

If you are using the Yarn feature zero-installs that was introduced in Yarn V2, note that this PR does not update the .yarn/cache/ directory meaning this code cannot be pulled and immediately developed on as one would expect for a zero-install project - you will need to run yarn to update the contents of the ./yarn/cache directory.
If you are not using zero-install you can ignore this as your flow should likely be unchanged.

⚠️ Warning

Failed to update the yarn.lock, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Uncontrolled Recursion SNYK-JS-BRACES-19963945	124

Breaking Change Risk

Notice: This assessment is enhanced by AI.

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Uncontrolled Recursion

[posit-snyk-bot]

This is a major upgrade from v5 to v8, introducing significant breaking changes across multiple versions that require substantial developer action, including environment upgrades and a complete configuration file migration.

v6.0.0 Breaking Changes:

• Environment: Dropped support for Node.js v12 & v14 and ESLint v6. The minimum required TypeScript version was bumped to 4.2.
• Configuration: The main configuration presets were renamed. For example, recommended-requiring-type-checking and strict were introduced, changing how rule sets are extended.
• Rules: Several previously deprecated rules were removed entirely.

v7.0.0 Breaking Changes:

• Environment: Support for Node.js 16 was dropped, requiring Node.js ^18.18.0 or >=20.0.0. The minimum required ESLint version was raised to ^8.56.0.
• Configuration: Introduced the typescript-eslint package to support ESLint's new flat config format (eslint.config.js), a fundamental change from the legacy .eslintrc files.

v8.0.0 Breaking Changes:

• ESLint v9 Support: This version ships with full support for ESLint v9.
• Configuration: The popular ban-types rule was removed and replaced by more specific rules like @typescript-eslint/no-empty-object-type and @typescript-eslint/no-restricted-types.
• Tooling: A new parserOptions.projectService feature was added to simplify TypeScript project configuration by automatically locating tsconfig.json files.

Recommendation:
This upgrade cannot be completed without significant manual intervention. A full migration of your ESLint configuration to the new flat config format is required. You must also ensure your Node.js version meets the new requirements. It is highly recommended to follow the official migration guides for each major version to address the configuration and rule changes.

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.

[posit-snyk-bot]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.