I apologise; I opened the issue without having finished writing it by accident.

Please feel free to delete this comment and fix the initial report.

The various Electron packages were removed from the blacklist in a recent commit (`de8f2e...`) and at least `electron16` is now in the repos.

community/electron18 and community/electron18 are in the repos and not blacklisted.
I would suggest to automatically blacklist every package with "electronX" in its name on release, X being any number(s) but not letters or other characters to avoid false positives when auto-blacklisting.

the blacklists are always maintained manually - an idea though, would be to modify libretools to allow regex or globbing of the package names; but that would prevent searching for entries by package name

eg:
electron*
firefox-addon-*
firefox-i10n-*

Isn't it possible to script the list generation?
What I mean is having wildcards being matched and expanded against arch repos, and then that match being piped into the blacklist.
That way it is possible to have wildcard entries while also not affecting package search.

Isn't it possible to script the list generation?

I thought it's already being scripted, sorry.
We can either script it, or throw all the future electron version packages (electron20, electron21, etc...) into the blacklist before they even exist just to be sure. Bothering with scripting, regex, and all that stuff will require effort.