cleveref is one of my favorite packages, and indeed, many of my own packages (cleveref-forward, crefthe, create-theorem) and classes (minimalist, colorist) depend in a fundamental way on cleveref.
However, it was last updated more than 5 years ago, and since then a lot have happened in the world of LaTeX. And I remember having seen patches to cleveref in many different places (but unfortunately I didn't take note on them; one could see some of these by viewing at those questions with tag "cleveref"). As a package maintainer, I am concerned about this situation (when I started to write my first package in 2021, this didn't seem to be quite a problem, but now one has to face the possibility that cleveref may no longer be maintained). For example, just recently I have added to one package a patch given by Ulrike Fischer in this answer.
Is there thus, to your knowledge, a collected list of known issues (and hopefully also recommended solutions) and known improvements to cleveref as for now? And for those newly coming users, is it still okay to use cleveref in their daily documents? And in case not, is there perhaps any alternative choice as for now?
zref-clever? This is such a nice work! Sadly I didn't notice it when I wrotecreate-theorem, otherwise I would probably usezref-cleveras its base package from the beginning. – Jinwen Feb 24 '24 at 20:41zref-cleveris an experimental package, in its early days. It should work well, but it may or may not meet your stability requirements. You may find this thread of interest: https://github.com/gusbrs/zref-clever/issues/9 – gusbrs Feb 24 '24 at 20:52\zcLanguageSetupand convert my old naming configuration into this form, and then add support tozref-clever. This way, the traditional\crefand the new\zcrefcan be coexisted, and the users can decide which to use in their documents. (To be frank, trying to make German declensions work withcleverefwas a struggle for me and I really don't want that effort to be wasted.) – Jinwen Feb 24 '24 at 21:16texdoc afterpagewith the number of times users expect that package to do something vaguely useful. – David Carlisle Feb 24 '24 at 22:50