Message from Friedrich Zahn via TSC & Projects on 2026-09-15 12:17:
Hi everyone,
the FOCIS team would like to raise some awareness that several ALASCA projects make use of mkdocs v1, which has not seen a release for 2 years. Its development has been halted by the original author, resulting in some rather ugly fallout & forks in the community[0]. v2[1] will not be compatible and follows a rather unconventional, closed governance approach[2]. Not having any license, it's currently not free software.
Affected ALASCA projects we've identified so far: - docs.alasca.cloud (ALASCA "governance" repo) - Arko - IXpect - Seconlay - Tarook (images/nginx-ingress)
As a first, quick measure we recommend pinning your mkdocs dependency (to anything <2), to prevent an unwanted upgrade & breakage.
If the ALASCA community comes up with a more concrete transition plan, we're happy to help implement it, especially for the ALASCA docs repo.
Best regards Friedrich
[0]: https://github.com/mkdocs/mkdocs/discussions/4010 https://github.com/orgs/ProperDocs/discussions/33 [1]: https://github.com/encode/mkdocs [2]: https://squidfunk.github.io/mkdocs-material/blog/2026/02/18/ mkdocs-2.0/ _______________________________________________ TSC & Projects mailing list -- tsc-projects@lists.alasca.cloud To unsubscribe send an email to tsc-projects-leave@lists.alasca.cloud
Hi Friedrich, thanks for turning this up. Regarding Tarook's images/nginx-ingress repository: This is just a manually reviewed mirror of github.com/chainguard-forks/ingress-nginx. mkdocs which they use in their CI pipeline is not used by us. Best regards, Bruno TAROOK Maintainer