apt 2.0.2 lacks * wildcard support

Upstream removed support for * as a wildcard in apt 2.0.0

They subsequently reinstated it in apt 2.1.0

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953531
https://lists.debian.org/deity/2020/03/msg00055.html
https://metadata.ftp-master.debian.org/changelogs//main/a/apt/apt_2.1.6_changelog

Will focal look to update apt to 2.1.x or backport this fix?

The lack of this simple syntax for using apt with wildcards really destroys the utility of apt on the command line.

Thanks

It doesn't destroy it at all and users can install and remove packages as needed....

I suggest you report a bug to show interest in it being reinstated but the feature being omitted destroys nothing. Try being less melodramatic

The first link in your question already gives a workaround:

This is intentional and was announced in debian/NEWS as well
as the recent email announcements. You can use patterns, e.g.
apt install ~n^remmina-plugin-

Thanks - I read the links before posting them.

No melodrama just an awful lot muscle memory to retrain to use the alternative syntax when installing or removing multiple packages and I just wanted to know if it was likely the upstream revert would come to Focal quickly or if we are stuck with the status quo.

Simple question needs a simple answer, and the bug is already reported.

"... and the bug is already reported."

Bug #1885410 "apt 2.0.2 lacks * wildcard support" is marked as invalid.
You cannot expect that anyone will still work on it if it is in that status.

I need to merge the security update into the bugfix release which I forgot about and reupload it to focal.

Thanks Julian Andres Klode, that solved my question.