Emma Marichal [Thu, 7 May 2026 16:07:10 +0000 (18:07 +0200)]
Montenegrin Gothic One: Version 1.002; ttfautohint (v1.8.4.16-eb64) added
Taken from the upstream repo https://github.com/MagicformDesign/montenegrin-gothic-one at commit https://github.com/MagicformDesign/montenegrin-gothic-one/commit/7a9c8500be19a4b3c6050dd4ea6fcf184ca59173.
Bitcount Single Ink: remove non-buildable config_yaml field
METADATA.pb's config_yaml pointed at the upstream sources/config.yaml,
which contains only "familyName: Bitcount" with no sources: field — not a
gftools-builder config. Bitcount is built by a custom Python/COLRv1
pipeline that gftools-builder cannot reproduce.
Removed the non-functional config_yaml field, addressing the
inconsistency noted in upstream_info.md. Repository URL, commit, branch
and file mappings are unchanged.
Bitcount Prop Single Ink: remove non-buildable config_yaml field
METADATA.pb's config_yaml pointed at the upstream sources/config.yaml,
which contains only "familyName: Bitcount" with no sources: field — not a
gftools-builder config. Bitcount is built by a custom Python/COLRv1
pipeline that gftools-builder cannot reproduce.
Removed the non-functional config_yaml field, addressing the
inconsistency noted in upstream_info.md. Repository URL, commit, branch
and file mappings are unchanged.
METADATA.pb's config_yaml pointed at the upstream sources/config.yaml,
which contains only "familyName: Bitcount" with no sources: field.
fontc_crater failed with "missing field `sources`".
Bitcount is built by a custom Python pipeline (Makefile -> scripts/build.py)
that generates designspace files from .stylespace definitions and adds
COLRv1 pixel layers — it cannot be expressed as a gftools-builder config.
Removed the non-functional config_yaml field. Repository URL, commit,
branch and file mappings are unchanged.
Noto Sans Duployan: remove non-buildable config_yaml field
METADATA.pb's config_yaml pointed at the upstream
sources/config-sans-duployan.yaml, whose sources: list names
NotoSansDuployan.glyphs. That file existed only transiently (2022-06 to
2023-01) and is absent at the recorded commit. fontc_crater failed with
"missing source 'NotoSansDuployan.glyphs'".
Noto Sans Duployan is a code-generated family built by a custom
Makefile/build.py pipeline, with no .glyphs/.ufo/.designspace source.
Removed the non-functional config_yaml field. Repository URL, commit,
archive_url and file mappings are unchanged.
Comic Relief: remove non-buildable config_yaml field
METADATA.pb's config_yaml pointed at the upstream sources/config.yaml,
which lists .ufo sources. The repo at the recorded commit contains only
FontForge .sfd files; the .ufo files are build artifacts of a non-gftools
"make convert" (sfd2ufo) step that gftools-builder cannot run.
fontc_crater failed with "missing source 'ComicRelief-Bold.ufo'".
Removed the non-functional config_yaml field. The family's upstream
sources are FontForge .sfd files, not gftools-builder compatible without
a separate conversion step. Repository URL, commit and archive_url are
unchanged.
The override config.yaml referenced sources: [Oxygen-Regular.ufo], a file
that does not exist anywhere in the upstream repo. fontc_crater failed
with "missing source 'Oxygen-Regular.ufo'".
The upstream vernnobile/oxygenFont repo is a legacy FontForge-era project;
the shipped Light weight has no UFO source at all (only a .sfd), so the
three-static family cannot be reproduced by gftools-builder. Removed the
misleading override config.yaml and documented the family as not
reproducible. METADATA.pb is unchanged.
The override config.yaml referenced sources: [NL.ufo], a file that does
not exist anywhere in the upstream repo. fontc_crater failed with
"missing source 'NL.ufo'".
The upstream anoxic/neuton repo is an in-progress personal project with
only FontForge .sfd masters and fragmentary partial UFOs — it has no
gftools-builder-compatible source set, and the shipped six-style family
cannot be reproduced from it. Removed the misleading override config.yaml
and documented the family as not reproducible. METADATA.pb is unchanged.
DM Sans: add corrected override config.yaml for fontc_crater build
The upstream config Sans/Source/config.yaml has valid content but every
line is indented 4 spaces with no top-level key, so it cannot be parsed.
fontc_crater failed with "no config file was found".
Added an override config.yaml: the upstream config de-indented to valid
top-level YAML, with source paths made repo-root-relative
(Sans/Source/DMSans.glyphs, Sans/Source/DMSans-Italic.glyphs). Removed the
config_yaml field from METADATA.pb so the override is auto-detected. The
recorded commit and sources are otherwise correct.
Fragment Mono: add override config.yaml for fontc_crater build
The upstream sources/config.yaml lives in sources/ and lists its source
as the bare path Fragment-Mono.glyphs, which only resolves relative to
the config's own directory. The build harness resolves source paths from
the repository root, so fontc_crater failed with "missing source
'Fragment-Mono.glyphs'".
Added an override config.yaml with the repo-root-relative source path
sources/Fragment-Mono.glyphs and removed the config_yaml field from
METADATA.pb so the override is auto-detected. The recorded commit is
correct.
Trykker: add override config.yaml for fontc_crater build
The upstream sources/config.yaml lists its source as "Trykker" with no
file extension; the actual source is the Glyphs 3 package directory
sources/Trykker.glyphspackage. fontc_crater failed with "missing source
'Trykker'".
Added an override config.yaml referencing sources/Trykker.glyphspackage
and removed the config_yaml field from METADATA.pb so google-fonts-sources
auto-detects the override. The recorded commit is correct.
Noto Serif Nyiakeng Puachue Hmong: fix override config source path
The override config.yaml referenced sources/NotoSerifNPHmong.designspace,
but the recorded commit (6f39c5843) predates the 2022-09-12 rename of the
source files from NotoSerifNyiakengPuachueHmong.* to NotoSerifNPHmong.*.
fontc_crater failed with "missing source
'sources/NotoSerifNPHmong.designspace'".
Corrected the config.yaml source path to
sources/NotoSerifNyiakengPuachueHmong.designspace. The recorded commit is
correct and was left unchanged.
Noto Naskh Arabic UI: fix override config source for fontc_crater build
The override config.yaml referenced sources/NotoNaskhArabicUI.glyphspackage,
but the recorded commit (133ccaeb, tag v2.014) predates the 2023-07-24
conversion to the .glyphspackage format. At that commit the source is the
flat file sources/NotoNaskhArabicUI.glyphs. fontc_crater failed with
"missing source 'sources/NotoNaskhArabicUI.glyphspackage'".
Corrected the config.yaml source path to sources/NotoNaskhArabicUI.glyphs.
The recorded commit is correct and was left unchanged.
Arsenal SC: fix override config source paths for fontc_crater build
The override config.yaml listed the Glyphs sources as Arsenal.glyphs and
Arsenal-Italic.glyphs without the sources/ directory prefix. At the
recorded commit (e34db566) the sources are sources/Arsenal.glyphs and
sources/Arsenal-Italic.glyphs. fontc_crater failed with "missing source
'Arsenal-Italic.glyphs'".
Corrected the config.yaml source paths to include the sources/ prefix,
matching the regular Arsenal family's config. The recorded commit is
correct and was left unchanged.
Abhaya Libre: fix source commit and config for fontc_crater build
METADATA.pb recorded commit f53da70 (2024-05-31) and config_yaml
"sources/config.yaml". The override config.yaml referenced
sources/glyphs/Abhaya-Masters.glyphs, which does not exist at f53da70,
so fontc_crater failed with "missing source
'sources/glyphs/Abhaya-Masters.glyphs'".
upstream_info.md already contained a detailed analysis recommending the
historically-accurate onboarding commit. Applied those recommendations:
- source.commit changed to ade314aa (2017-02-16), one day before the
fonts were added via google/fonts PR #665 (v1.050). The override
config's source path sources/glyphs/Abhaya-Masters.glyphs exists at
this commit.
- Removed config_yaml field: sources/config.yaml does not exist at the
onboarding commit (it was introduced upstream in 2024); the local
override is auto-detected.
The alternative of keeping f53da70 would build the 2024 variable-era
sources, which do not correspond to the shipped 2017 static binaries.
Mogra: fix override config source path for fontc_crater build
The override config.yaml listed the Glyphs source as Mogra.glyphs at the
repository root, but at the recorded commit (048039d) the source is
sources/Mogra.glyphs. fontc_crater failed with "missing source
'Mogra.glyphs'".
Corrected the config.yaml source path to sources/Mogra.glyphs. The
recorded commit is correct and was left unchanged.
Kumar One Outline: fix override config source path for fontc_crater build
The override config.yaml listed the Glyphs source as "Kumar One.glyphs"
at the repository root, but at the recorded commit (3192a79) the source
is "masters/Kumar One.glyphs". fontc_crater failed with "missing source
'Kumar One.glyphs'".
Corrected the config.yaml source path to "masters/Kumar One.glyphs". This
is the same itfoundry/kumar source shared with the Kumar One family. The
recorded commit is correct and was left unchanged.
Kumar One: fix override config source path for fontc_crater build
The override config.yaml listed the Glyphs source as "Kumar One.glyphs"
at the repository root, but at the recorded commit (3192a79) the source
is "masters/Kumar One.glyphs". fontc_crater failed with "missing source
'Kumar One.glyphs'".
Corrected the config.yaml source path to "masters/Kumar One.glyphs".
The recorded commit is correct and was left unchanged.
Yatra One: fix override config source path for fontc_crater build
The override config.yaml listed the UFO source as YatraOne_0.ufo at the
repository root, but at the recorded commit (b991e49) the source is
source/masters/YatraOne_0.ufo. fontc_crater failed with "missing source
'YatraOne_0.ufo'".
Corrected the config.yaml source path to source/masters/YatraOne_0.ufo.
The recorded commit is correct and was left unchanged.
Sriracha: fix override config source path for fontc_crater build
The override config.yaml listed the UFO source as Sriracha-Regular.ufo
at the repository root, but at the recorded commit (6c6cf92) the source
is source/Sriracha-Regular.ufo. fontc_crater failed with "missing source
'Sriracha-Regular.ufo'".
Corrected the config.yaml source path to source/Sriracha-Regular.ufo.
The recorded commit is correct and was left unchanged.
Pragati Narrow: fix override config source path for fontc_crater build
The override config.yaml listed the Glyphs source as PragatiNarrow.glyphs
at the repository root, but at the recorded commit (829be32) the source
is SRC/PragatiNarrow.glyphs. fontc_crater failed with "missing source
'PragatiNarrow.glyphs'".
Corrected the config.yaml source path to SRC/PragatiNarrow.glyphs. The
recorded commit is correct and was left unchanged.
Barrio: fix stale source commit hash for fontc_crater build
The recorded source.commit (ced3c1e, 2015-02-03) predated the Google
Fonts onboarding by ~22 months; at that commit the Glyphs source was
still at SRC/Barrio.glyphs. The override config.yaml references
sources/Barrio.glyphs, so fontc_crater failed with "missing source
'sources/Barrio.glyphs'".
Updated source.commit to 4cb00e5 (2016-12-04), the last upstream commit
before the google/fonts PR #491 merge, where sources/Barrio.glyphs
exists. This commit was already identified as correct in upstream_info.md
but the METADATA.pb field had never been updated.
Lalezar: fix source commit hash for fontc_crater build
The recorded source.commit (c3e0eae, Aug 2016) predates the creation of
the sources/ directory in the upstream repo. fontc_crater failed with
"missing source 'sources/Lalezar.glyphs'" because config.yaml references
a path that does not exist at that revision.
Updated source.commit to 238701c (Feb 28 2017) — the last upstream
commit before the google/fonts binary date, matching date_added
(2017-02-28), where sources/Lalezar.glyphs exists at the canonical path.
The previous value came from a tag_match heuristic that matched a
version tag without verifying the build source existed at that revision.
Emma Marichal [Thu, 21 May 2026 09:23:21 +0000 (11:23 +0200)]
Pliant: Version 1.000 added
Taken from the upstream repo https://github.com/TheJonassss/Pliant at commit https://github.com/TheJonassss/Pliant/commit/dc119b45f0b60597305af387b97b2f5a94b2e1e4.
Geist Mono: Version 1.701 (hotfix for liga regression in 1.700)
Drops the `liga` (Standard Ligatures) OpenType feature that was
unintentionally introduced in v1.700 (#10407). `liga` is on by
default in every OpenType renderer, so the programming-ligature
substitutions added in vercel/geist-font@6ad0ea2 were firing
against source-code text — e.g. `--debug-prerender`, `[id...]`,
`[...id]`, `NODE_OPTIONS='--debug-prerender' node`.
The regression was reverted upstream in vercel/geist-font#217.
This PR pulls the post-revert artifacts: source.commit is bumped
to vercel/geist-font@77f0563c. fontRevision goes 1.700 -> 1.701;
all other OpenType features (aalt, case, ccmp, dnom, frac, locl,
numr, ordn, sinf, ss01-ss11, subs, sups) and glyph counts are
unchanged.
Emma Marichal [Fri, 15 May 2026 10:16:03 +0000 (12:16 +0200)]
Merge commit '49fffabc01c3b6f419754d16679814ddda379501' into axisregistry-v0.4.17
# Please enter a commit message to explain why this merge is necessary,
# especially if it merges an updated upstream into a topic branch.
#
# Lines starting with '#' will be ignored, and an empty message aborts
# the commit.
Arpit Jain [Wed, 13 May 2026 07:27:09 +0000 (07:27 +0000)]
ci: declare contents: read in four pure-CI workflows
ci.yaml, designers.yaml, font_tags.yaml, and pushlists.yaml all just check
out the repo, run python validators, and either succeed or fail. None push,
comment, or call write APIs.
scorecard.yml in this repo already declares permissions: read-all at the
workflow level; the four files in this PR were the remaining ones still
running with the repo default token scope.
projects / thirdparty / google / fonts.git / log
