Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Scheduled weekly dependency update for week 13 #3472

Merged
merged 3 commits into from
Apr 1, 2024

Conversation

pyup-bot
Copy link
Collaborator

@pyup-bot pyup-bot commented Apr 1, 2024

Update ufo2ft from 3.1.0 to 3.2.0.

Changelog

3.2.0

- Some bug fixes and better error handling while building MATH table (820).
- Fixed a error while building variable GDEF ligature carets (821).
- Added new ``ufo2ft.instantiator`` module, copied over from ``fontmake.instantiator`` and adapted to also work on defcon Font objects, in addition to ufoLib2.Font (825).
- Support compiling variable TTF or CFF2 fonts with 'sparse' composite glyphs which define either more or fewer sources than the glyphs used as components. We use the instantiator to interpolate glyphs on the fly while decomposing, or we add empty placeholders in TTF masters for missing components in the non-default masters so the sparse composites can be built with varLib (googlefonts/glyphsLib954, 826).

3.2.0b1

TODO
Links

Update glyphsLib from 6.6.6 to 6.7.0.

Changelog

6.7.0

- Removed ``resolve_intermediate_components`` from the preflight stage, since this is no longer needed now that ufo2ft v3.2.0 will handle this at build time (only if/when actually needed).
See https://github.com/googlefonts/ufo2ft/releases/tag/v3.2.0

6.7.0b1

TODO
Links

Update lxml from 5.1.0 to 5.2.0.

Changelog
Links

@khaledhosny khaledhosny merged commit 43467f1 into main Apr 1, 2024
11 checks passed
@khaledhosny khaledhosny deleted the pyup-scheduled-update-2024-04-01 branch April 1, 2024 18:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants