Closed guidoferreyra closed 3 months ago
One sec, I'll update the package in this PR too.
Gonna publish to 1.3.0 instead of 1.2.0 since the latter was used already.
One sec, I'll update the package in this PR too.
Gonna publish to 1.3.0 instead of 1.2.0 since the latter was used already.
So I guess, we should bump the version number on the fonts too.
Or maybe since the release has been already published we can do it on the next update. What do you think?
@guidoferreyra For the release yesterday
Where else do we need to update the version number?
The version number in the font binaries, is on the font table data.
@JohnPhamous this pull request includes many changes with fixes and enhancements. With this changes merged we can release version 1.3.0. These are the corresponding binaries.
GeistMono-1.2.0.zip Geist-1.2.0.zip
I have a draft for the release ready to be published after the merge, but let me know if you need to make changes on the npm package first.
Noteworthy changes