[Typst Universe] Automatically label packages as "working"/"not working" if their template builds using the latest version of Typst

[mewmew]

Description

It's quite incredible how the Typst Universe is expanding on a daily basis.

As of today there are 3000 merged PRs in the typst/packages repo!

A victim to its own success, since there are now so many packages on the Typst Universe. As a user it becomes more difficult to find good (and working) templates.

As one step in improving the situation, it would be useful to automatically label template packages as "working"/"not working", based on if the template compiles using the latest version of Typst.

There are several template packages that don't seem to compile using the latest version of Typst. For instance:

• https://typst.app/universe/package/tud-corporate-design-slides

• https://typst.app/universe/package/academic-conf-pre

• https://typst.app/universe/package/touying-pres-ustc

There are also template packages that don't seem to compile due to missing resource files, e.g.

• https://typst.app/universe/package/gqe-lemoulon-presentation

And as such, when e.g. using the Typst.app webapp and creating a new project based on these templates, the user can be faced with an error which they cannot solve, since they don't have access/possibility to edit the template source code (at least not in an easy way).

So, to add a label where one can filter for packages that are known to compile successfully (with the latest version of the Typst compiler) would be great for Typst Universe users!

[mewmew]

Adding some discussions from Discord.

From dany (https://discord.com/channels/1054443721975922748/1054443722592497796/1420943025173172254):

curious, but why are templates allowed to be published to typst universe when they are buggy / do not compile, is there not some sort of standard CI/CD they have to pass? (in reference to tufte-memo:0.1.2)

From @mentonin (https://discord.com/channels/1054443721975922748/1054443722592497796/1420945259973705840):

Typst could retest every template on each new version, and mark ones that don't compile

From @mentonin (https://discord.com/channels/1054443721975922748/1054443722592497796/1420965270180204574):

I think automatically flagging templates that stop compiling isn't much work for the typst team nor for the package developers. It is also useful for package developers, who might otherwise take longer to find out a problem, and for the typst team, who can use it as a measure of regression

[mewmew]

Collecting some data-points where this would have been handy to help catch template build errors:

• cob-unofficial:0.1.0 (fix in RP cob-unofficial:0.1.1 #3143)
• efter-plugget:0.1.0 (fix in PR efter-plugget:0.1.1 #3130)