Since this is indeed a breaking change, we're highly unlikely to ever merge it unless there's avery compelling reason.

How does the linked bug impact this plugin?

Thank you for your quick response!

For example, I want to loosen rules a bit for testing, but I can't.

module.exports={plugins:['import'],rules:{'import/no-internal-modules':['error',{forbid:['@src/a/*/**']}],},overrides:[{files:['src/**/*.test.ts'],rules:{'import/no-internal-modules':['error',{forbid:['@src/a/*/!(__tests__)/**']}],}}]}

As a user, it's very reasonable we can use glob expressions correctly.
I know backward compatibility may concern you as a maintainer. I'll close this PR if there is another workaround

I'm quite unfamiliar with inline glob expressions like that - do they work in gitignore?

As such, I have no idea what you're trying to forbid - and allow - with that glob. Can you elaborate?