Rik Smale

Ah yes, this was already mentioned in #14408 This was introduced in #13347 and I think it's a good change but we just need to see if we can return...

Thanks for bringing this to our attention. I already thought there was something strange with this, although we haven't changed anything to the [config of the GitHub actions for this](https://github.com/sequelize/sequelize/blob/main/.github/workflows/stale.yml)....

Might be related to https://github.com/actions/stale/pull/775 btw

Yeah, the bot is quite aggressive. I have added the `type: bug` label and now it won't mark it as stale anymore. It would be great if you could provide...

@sdepold ping. This coment probably explains the questions you had earlier; https://github.com/sequelize/sequelize/pull/13647#issuecomment-985953590

@sudarshan12s sorry for the long wait, but I hope to be able to take another look at this later this week

I'm fine with adding 18.4 CI testing in a separate PR. I think that with these latest change we should be good to go. @sdepold agree?

@ephys I'm clearing up my notifications and trying to ping you in some of those so they're back on your radar

Can you add that error as the expected response from those dialects?

Yeah, just add a different expectation in the test itself