Skip to content

Bump skrifa to 0.48 and write-fonts to 0.54 - #38

Open
gastongouron wants to merge 1 commit into
typst:mainfrom
gastongouron:bump-fontations
Open

gastongouron wants to merge 1 commit into
typst:mainfrom
gastongouron:bump-fontations

Conversation

@gastongouron

Copy link
Copy Markdown

Bumps skrifa 0.42 -> 0.48 and write-fonts 0.48 -> 0.54 (read-fonts 0.45 underneath), plus the matching dev-dependency and the fuzz crate. kurbo 0.13 is still what write-fonts 0.54 wants, so it stays.

Motivation: subsetter is now the only crate in our tree still on skrifa 0.42. resvg/usvg moved to 0.44 and harfrust is on read-fonts 0.41, so anything that subsets with this crate and renders with those ends up compiling two fontations stacks. Getting subsetter onto current skrifa lets the rest of the ecosystem share one.

No code changes were needed. Checked locally:

  • cargo test with fonttools on PATH: 175 passed, same result as before the bump
  • cargo clippy --workspace --all-targets --all-features and cargo fmt --check --all clean
  • cargo check --workspace on 1.85.0 (fontations crates declare rust-version 1.85, so the MSRV holds)

@yhay81

yhay81 commented Oct 23, 2026

Copy link
Copy Markdown

Thanks for this! skrifa 0.49 and write-fonts 0.55 were released on October 21 and use read-fonts 0.46, the same version as HarfRust 0.15, so bumping one step further would let subsetter share a single read-fonts with current HarfRust and skrifa users. It needs no code changes either; I tried it on top of main: yhay81@1fca778

  • cargo test with fonttools 4.62 and CFFDump 1.3.0, as in CI: 175 passed, and the ttx/cff outputs in tests/ are unchanged
  • cargo clippy --workspace --all-targets --all-features -- -D warnings, cargo fmt --check --all, cargo doc --workspace --no-deps on 1.89.0, cargo build --no-default-features
  • cargo check --workspace on 1.85.0 (skrifa 0.49 and write-fonts 0.55 still declare 1.85)

Would you like to update this PR to those versions? If you'd rather keep it as is, I can open a follow-up PR after this one is merged.

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.

2 participants