v0.21.1 — Pixel-native default resolution

A patch release: a saner default resolution for the raster backends.

The default dpi on the image backends is now 72 instead of 100

CairoImageTypesetter (Native) and Graphics2DTypesetter (JVM) apply a device transform of dpi / 72 when mapping the engine's point coordinates onto their pixel surface. The default was 100, a value that silently scaled every layout by 100/72 ≈ 1.389× — so an embedder who set paperwidth = 1280 and constructed a backend with no argument got a 1778-pixel surface.

The default is now 72, so the device transform is the identity and one point renders as exactly one pixel: a page of N points is an N-pixel image, with no hidden scaling. This is the least-surprising default for a library whose raster output is mostly pixel-native (video frames, GPU textures, GUI previews), and it matches the point-native PDF backend so switching PDF↔PNG no longer rescales coordinates. Pass a higher dpi (e.g. 144 or 216) to supersample the same layout for crisper output.

This only affects code that constructs a raster backend without a dpi argument. The command-line tool is unaffected — it always passes an explicit resolution (-r, default hd) — and every test already passed an explicit value.

Suites are green at JVM 1360 / JS 1234 / Native 1250.

Native CLI binaries for Linux (x86_64, arm64) and macOS (arm64) attach below; other platforms use the JVM build.