This issue was prompted by the release of ESLint v9
Since there are a lot of packages at play here, that are all updated individually, it's easy to reach a configuration that does not play nicely together (e.g. typescript-eslint v7 with @next/eslint-plugin-next which is simply just incompatible since the next plugin requires typescript-eslint v6).
By setting up a small project that uses @atmina/linting as dependency and a little GitHub Action to try and lint that project using this package, we can easily spot which upgrades contain breaking changes and which are incompatible with each other. That way, we can prevent renovate from upgrading dependencies that would break the plugin if released.
This issue was prompted by the release of ESLint v9
Since there are a lot of packages at play here, that are all updated individually, it's easy to reach a configuration that does not play nicely together (e.g. typescript-eslint v7 with @next/eslint-plugin-next which is simply just incompatible since the next plugin requires typescript-eslint v6).
By setting up a small project that uses @atmina/linting as dependency and a little GitHub Action to try and lint that project using this package, we can easily spot which upgrades contain breaking changes and which are incompatible with each other. That way, we can prevent renovate from upgrading dependencies that would break the plugin if released.