Milos Djermanovic

> This implements the [additional deprecated metadata RFC](https://github.com/eslint/rfcs/blob/02ba56c5ec0f84b8861fc70642b6b26181c73c45/designs/2024-deprecated-rule-metadata/README.md) and closes #18053. I think this closes https://github.com/eslint/eslint/issues/18061 but not #18053.

> As noted in the notes I did not need to update the website code to keep working (it looks the same as without the changes). > Which additional details...

@DMartens can you please resolve merge conflicts?

Verify Files check is failing: ``` Validating rules Missing deprecated information in yield-star-spacing rule code or README.md. Please write @deprecated tag in code and「This rule was deprecated in ESLint ...」...

Links to replacement rules are now missing on the rules reference page. For example, on https://eslint.org/docs/latest/rules/:  On https://deploy-preview-19238--docs-eslint.netlify.app/rules/: 

Sounds good to me too 👍

> it would be nice to get the packages transitioned to ESM All three packages are already ESM. In that regard, a difference between these and eslint/rewrite packages is only...

> "eslint-plugin-next": "^0.0.0", It seems that you are using a package that doesn't have any content other than `package.json`: https://www.npmjs.com/package/eslint-plugin-next?activeTab=code I'm guessing you should use `@next/eslint-plugin-next` instead: https://www.npmjs.com/package/@next/eslint-plugin-next In your...

No response, so closing.

> I've updated the PR so that BOMs are not passed to processors any more. Makes sense to me. It seems unlikely that a processor would particularly want to know...