Update dependency fontbakery to >=0.11.2 #155
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
>=0.9.2->>=0.11.2Release Notes
fonttools/fontbakery (fontbakery)
v0.11.2Compare Source
Release Notes
v0.11.1Compare Source
Release highlights & new features
-q--quietCLI option to suppress all terminal output. (issue #4484)Changes to existing checks
On the Universal Profile
v0.11.0Compare Source
Noteworthy code-changes
New checks
Added to the Universal Profile
Added to the Google Fonts Profile
Previously experimental checks now made effective
The dates indicate when each check was originally implemented as temporarily experimental.
Promoted on Universal profile
Promoted on Google Fonts profile
Migration of checks
Moved to the Google Fonts profile
Changes to existing checks
On the Universal Profile
ttFont.getBestCmap()to avoid potential ERROR. (issue #3601)On the OpenType Profile
On the Shaping Profile
On the Google Fonts Profile
gfsubsetspackage. (PR #4434)v0.10.9Compare Source
--skip-networkto skip any checks which require Internet access. (PR #4387)New checks
Added to the OpenType Profile
Changes to existing checks
On the Shaping profile
On the OpenType profile
On the Google Fonts Profile
On the TypeNework Profile
v0.10.8Compare Source
--error-code-onto define the threshold for emitting error code 1. By default, the FontBakery process still communicates an error code 1 if there's any check resulting in FAIL or worse. But with this flag, the user (for instance, in a continuous integration setup) can change the behaviour, such as making a CI job break only when getting a FATAL check-result (or, alternatively, making it even stricter by also breaking CI jobs on WARNs). (PR #4376)Changes to existing checks
On the Google Fonts Profile
v0.10.7Compare Source
Changes to existing checks
On the Google Fonts Profile
On the Universal Profile
v0.10.6Compare Source
Note-worthy code changes
setup.py, so that only their latest available packages are acceptable for installation. Thanks @yanone for noticing and reporting this issue. (issue #4351)v0.10.5Compare Source
Note-worthy code changes
Changes to existing checks
On the Open Type Profile
On the Universal Profile
On the Google Fonts Profile
v0.10.4Compare Source
Note-worthy code changes
Changes to existing checks
On the Universal Profile
On the Google Fonts Profile
v0.10.3Compare Source
New checks
Added to the Google Fonts Profile
Changes to existing checks
On the OpenType profile
posttable. (issue #3839)On the Google Fonts Profile
v0.10.2Compare Source
New checks
Added to the Universal Profile
Changes to existing checks
On the Universal Profile
v0.10.1Compare Source
New checks
Added to the Universal Profile
Changes to existing checks
On the Google Fonts Profile
v0.10.0Compare Source
Release notes
This release adds support for marking checks as experimental, which will make them not affect the process exit code and so will allow such checks to result in a FAIL without breaking continuous integration builds. This will give time for users to report problems on the implementation of new checks. If after some time nobody complains, then those new checks will more safely be made effective by removing their
experimentaltag.Bugfix: Display informative message when users forget to install the
extraneeded for the vendor-specific profile they're trying to run (issue #4292)New checks
Added to the Google Fonts Profile
Changes to existing checks
On the Google Fonts Profile
startswithmethod on NoneType. Also upgrade check to FAIL and report any links with empty text content. (issue #4283)On the Universal Profile
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.