Runs fine on my pi. I know #3162 (which this replaces) was tagged with the 3.11.0 milestone, but is there any reason this PR couldn't go straight in now?

Any idea what's caused this in the CodeQL check?

However, the "11" rather than the "14" indicates success.

I'm happy for it to go into 3.10.0 as it's not going to affect translations or behaviour.

Any idea what's caused this in the CodeQL check?

No, I was going to ask about it. I'll do a bit of digging.

I think it's something to do with the autobuild efficiency changes introduced by @hoffie in 51830196b, but I don't really understand what's happening there.

OK, it's probably not something this issue/PR needs to worry about. Maybe raise a new issue?

@ann0see Are you okay with #3161 to 3.10.0 along with this?

Yes. I'll have a look at it.

Needs a changelog entry

Needs a changelog entry

I've lost track of what is now automated and what isn't. Does the "CHANGELOG" line in the above description make anything happen automatically?

There is a script which does the update but as the change log was manually edited (for merging multiple PRs) we need to add the last few entries manually.

we need to add the last few entries manually.

OK, do we know what else is missing, or does someone need to check? I'm happy to look, but won't have time till Friday.

That's fine. I believe only some Weblate PRs are missing

@ann0see So can the "needs documentation" label be removed here?

It still needs a change log entry.

That's part of the release process, not the documentation cycle. If something needs editing that we've already generated for the release, it should be documented under the release ticket, not here. Normally automatic Changelog generation would be used, it's only because we're in change freeze that something special is needed.

Ok. My error then.