Bot instructions don't say when we can close the bot issue

The instructions can't predicts if there will be increased deprecated API coverage or bugs fixed in the rector or phpstan rules, so it can't tell you if there is definitely not going to be any more fixes posted. It is up to you when you feel good enough about your own project compatibility. Should that explicitly be called out in the text?

Could there be more D10 update patches now that D10 is released?

Or will the bot post D11 update patches to that same issue?

The bot will not post Drupal 11 compatibility patches to the issues it opened with the "ProjectUpdateBotD10" tag (titled "Automated Drupal 10 compatibility fixes", although the title does not matter in matching).

Ok, so at what point will the D10 bot stop looking for issues to post patches to? That's what the issue text needs to tell maintainers.

I don't think we know that yet, @bbrala is working on integrating the bot into project_analysis instead of a one-off github project and I don't know if all work is halted for good on Drupal 9 to 10 deprecated API related code.

Also moving to the specific queue.

> I don't think we know that yet

Ok so maybe the instructions that the bot posts to an issue should have a link to somewhere that has latest status of the bot, such as whether it's still running or has been retired.

I'd suggest the bot's user profile page -- but that produces a 500 error!!!!

Fair enough. The goal is that the bot wil never stop running. We are currently working on getting d11 readiness up and running. See #3371547: [PLAN] Project update bot: road to Drupal 11 → . This will be new issues though.

Also there are still fixes that might emerge since we don't have full d9 coverage yet. So it might add more.

To be honest, I would probably keep the bot running for d10 for a while, even until after d11 is released.

My current view is the following:

The bot will run analyzing all project that support a supported version of drupal. Do we need anything more in this issue?

Do the bot instructions say that?

What about the ProjectUpdateBotD10 tag -- will there be an 11 tag, or a generic 'latest' tag?

There is a ProjectUpdateBotD11 tag yeah.