Last 12 weeks · 60 commits
3 of 6 standards met
Hi @christopherkindl, The latest release is tagged as 1.7.0, but the internal version of the Geist and Geist Mono fonts is 1.8.0. Additionally, Geist Pixel is currently at 1.0, which means the repository contains fonts with different version numbers under a single release. This makes version tracking and downstream usage a bit confusing. I previously mentioned this, but I understand that keeping the npm package managed from a single repository was a priority at the time. Suggestion:** Consider splitting releases by font family and version, for example: A release for Geist Pixel 1.0.0 A separate release for Geist / Geist Mono 1.8.0 This is similar to how versioning is handled in other large font repositories, such as IBM Plex: https://github.com/IBM/plex/releases This approach would make versioning clearer and easier to manage for users consuming the fonts directly.
Repository: vercel/geist-font. Stars: 3288, Forks: 95. Primary language: HTML. Languages: HTML (99.5%), Makefile (0.3%), Python (0.2%). License: OFL-1.1. Homepage: https://vercel.com/font Topics: font, variable-fonts. Latest release: geist@1.7.0 (3w ago). Open PRs: 2, open issues: 36. Last activity: 1w ago. Community health: 62%. Top contributors: guidoferreyra, JohnPhamous, christopherkindl, ZeeJab, zacowan, almonk, ypessoa, vv-monsalve, bkonkle, github-actions[bot] and others.
HTML
Context When doing releases, we experienced 2 issues: 1. Flakiness in the build, where triggering a new workflow appeared to resolve the issue: https://github.com/vercel/geist-font/actions/runs/21756393942/job/62767735684 2. was not respecting : https://github.com/vercel/geist-font/actions/runs/21759363287/job/62781569308 Solution 1. Remove the cache. This should hopefully prevent the flakiness and I'm not really sure that we save much time anyways. 2. Pin the version of to a previous version where was working (see https://github.com/changesets/action/issues/501)