Releases: petipoua/petiglyph
v0.1.5
petiglyph
Summary
- Version:
0.1.5 - Date:
2026-06-09 - Release type: patch
This patch release focuses on Windows font installation reliability. Installed
fonts are now registered in the current-user Windows Fonts registry and loaded
through the Windows font APIs so they behave like real user-installed fonts
instead of only being copied into petiglyph-managed storage. The release also
documents the Windows Terminal fallback-family setup needed to render petiglyph
glyphs alongside a primary terminal font.
Changes
- Windows font install now writes the installed family into
HKCU\\Software\\Microsoft\\Windows NT\\CurrentVersion\\Fontsand registers
the TTF withAddFontResourceExW, making the font discoverable as a
user-installed Windows font. - Windows font uninstall now removes the loaded font resource and deletes the
matching current-user Fonts registry entry when present. - Added README guidance for Windows Terminal 1.21+ to configure a petiglyph
family as a fallback font after the primary terminal font, for example
"Cascadia Mono, my-font Petiglyph".
Compatibility
- CLI/API breaking changes: none
- Migration required: none
Distribution
Prebuilt GitHub and npm binaries are provided for:
- Linux GNU on x86-64 and ARM64
- Linux musl on x86-64 and ARM64
- macOS on Intel and Apple Silicon
- Windows on x86-64 and ARM64
PyPI provides Linux GNU manylinux, macOS, and Windows wheels plus a source
distribution. The AUR package requires ffmpeg and fontconfig.
macOS and Windows artifacts are unsigned.
v0.1.4
petiglyph
Summary
- Version:
0.1.4 - Date:
2026-06-09 - Release type: patch
This release is primarily a documentation and wording update on top of
v0.1.3. It adds a detailed tuning reference to the README, syncs agent-facing
repo instructions with the current CLI/TUI contract, and replaces the Th
abbreviation with Threshold in the Home creation workflow popup. There are no
behavioral CLI, JSON API, build-output, install, or font-runtime changes.
Changes
- Added a new README tuning reference that explains threshold, invert,
grayscale preprocessing, rows, columns, bleed, FPS, and project-level
rendering knobs such asglyph_size,codepoint_start,input_dir, and
out_dir. - Documented the actual defaults, accepted ranges, and practical visual effect
of each image-processing control so users can predict how a change will alter
imported imagery before rebuilding. - Updated agent-facing repo guidance to match the current project terminology,
CLI/TUI contract, code layout, generated paths, TUI guardrails, andhty
E2E workflow expectations. - Consolidated dependency supply-chain guidance into the current docs layout.
- Replaced the abbreviated
Thlabel withThresholdin the Home creation
workflow popup for wording consistency.
Compatibility
- CLI/API breaking changes: none
- Migration required: none
Distribution
Prebuilt GitHub and npm binaries are provided for:
- Linux GNU on x86-64 and ARM64
- Linux musl on x86-64 and ARM64
- macOS on Intel and Apple Silicon
- Windows on x86-64 and ARM64
PyPI provides Linux GNU manylinux, macOS, and Windows wheels plus a source
distribution. The AUR package requires ffmpeg and fontconfig.
macOS and Windows artifacts are unsigned.
v0.1.3
petiglyph
Summary
- Version:
0.1.3 - Date:
2026-06-09 - Release type: patch
This release is primarily a documentation and wording update on top of
v0.1.2. It adds a detailed tuning reference to the README, syncs agent-facing
repo instructions with the current CLI/TUI contract, and replaces the Th
abbreviation with Threshold in the Home creation workflow popup. There are no
behavioral CLI, JSON API, build-output, install, or font-runtime changes.
Changes
- Added a new README tuning reference that explains threshold, invert,
grayscale preprocessing, rows, columns, bleed, FPS, and project-level
rendering knobs such asglyph_size,codepoint_start,input_dir, and
out_dir. - Documented the actual defaults, accepted ranges, and practical visual effect
of each image-processing control so users can predict how a change will alter
imported imagery before rebuilding. - Updated agent-facing repo guidance to match the current project terminology,
CLI/TUI contract, code layout, generated paths, TUI guardrails, andhty
E2E workflow expectations. - Consolidated dependency supply-chain guidance into the current docs layout.
- Replaced the abbreviated
Thlabel withThresholdin the Home creation
workflow popup for wording consistency.
Compatibility
- CLI/API breaking changes: none
- Migration required: none
Distribution
Prebuilt GitHub and npm binaries are provided for:
- Linux GNU on x86-64 and ARM64
- Linux musl on x86-64 and ARM64
- macOS on Intel and Apple Silicon
- Windows on x86-64 and ARM64
PyPI provides Linux GNU manylinux, macOS, and Windows wheels plus a source
distribution. The AUR package requires ffmpeg and fontconfig.
macOS and Windows artifacts are unsigned.
v0.1.2
petiglyph
Summary
- Version:
0.1.2 - Date:
2026-06-09 - Release type: patch
This release improves multi-registry release reliability and fixes README
rendering on PyPI and npm. There are no CLI or TUI behavior changes.
Package Descriptions
- Fixed the demo image and video links in the PyPI description by using
absolute GitHub asset URLs. - Expanded the npm meta-package description to include the full repository
README after its npm-specific installation and platform-package guidance. - Added deterministic npm README generation from the canonical repository
README. - Added release hygiene checks that reject a stale generated npm README.
Release Reliability
- Made same-version release retries resume from the immutable tagged commit
whenmainhas advanced. - Corrected GitHub artifact verification to validate each asset's provenance
attestation and tagged source digest. - Added visible per-package progress while waiting for npm, PyPI, and AUR
registry propagation. - Made the public AUR cgit metadata authoritative during verification while
treating delayed AUR RPC indexing as informational. - Prevented long-running releases from reading a script modified during
execution by running from an immutable temporary snapshot.
Distribution
Prebuilt GitHub and npm binaries are provided for:
- Linux GNU on x86-64 and ARM64
- Linux musl on x86-64 and ARM64
- macOS on Intel and Apple Silicon
- Windows on x86-64 and ARM64
PyPI provides Linux GNU manylinux, macOS, and Windows wheels plus a source
distribution. The AUR package requires ffmpeg and fontconfig.
macOS and Windows artifacts are unsigned.
v0.1.1
petiglyph
Summary
- Version:
0.1.1 - Date:
2026-06-08 - Release type: patch
This release reorganizes the automation CLI around explicit project selection,
adds safer batch project and font management, expands project discovery, and
hardens the GitHub, npm, PyPI, and AUR release pipelines.
Highlights
- Added
new-projectanduse-projectas the primary automation workflow. - Consolidated glyph, grid, and animation imports under four creation types
matching the TUI workflows. - Added source configuration commands for thresholds, inversion, grids,
animation timing, and bleed. - Made installation explicit: creation imports content by default,
--build
generates artifacts, and--installadditionally installs the font. - Added structured project and installed-font listings with warnings for stale
or malformed state. - Added validated batch project deletion and exact-family font uninstall.
- Expanded project discovery through two directory levels without following
directory symlinks. - Normalized project paths across operating systems.
CLI Contract
The automation CLI changed substantially from v0.1.0.
Added top-level commands:
petiglyph new-project NAMEpetiglyph use-project PROJECT ...petiglyph list projectspetiglyph list installed-fontspetiglyph delete-project PROJECT...
Project-scoped operations now include:
create glyphcreate grid-glyphcreate animated-glyphcreate animated-grid-glyphconfigure glyphconfigure grid-glyphconfigure animationdelete animationbuildinstall-fontshow-sampledoctortui
Behavior changes:
- Project selection uses an exact project directory basename.
- Duplicate project basenames are rejected with candidate paths.
--inputaccepts multiple paths for creation commands.- Creation no longer installs automatically.
--installimplies--build.show-sampleonly reads the existingbuild/glyph-sample.txt; it does not
build or install.- Batch deletion and uninstall validate every target before modifying files.
list installed-fontsreports the exact family identifier accepted by
uninstall-font.
JSON API Schema Changes
The top-level JSON envelope remains:
okcommandversiondataerroron failure
Command identifiers now follow the project-oriented hierarchy, including:
list.projectslist.installed-fontsdelete-projectuse-project.create.glyphuse-project.create.grid-glyphuse-project.create.animated-glyphuse-project.create.animated-grid-glyphuse-project.configure.glyphuse-project.configure.grid-glyphuse-project.configure.animationuse-project.show-sample
Project listings now include directory name, relative path, font name, manifest
path, project ID, and malformed-manifest warnings. Installed-font listings now
include family, ownership, TTF path, manifest path, and stale metadata or
artifact warnings.
Failures continue to return a non-zero exit code and include an error message
with nested causes.
Font Lifecycle
- Installation is always explicit.
- Exact managed font families can be uninstalled directly.
- Multiple uninstall targets are validated before any font files or metadata
are removed. - Managed font cache and alias state are refreshed after uninstall.
Integrator Impact
This release contains breaking automation CLI changes.
Scripts written for v0.1.0 should migrate from manifest-scoped command families
to project-scoped commands. Typical migrations include:
petiglyph create my-font
petiglyph new-project my-font
petiglyph build --manifest my-font/petiglyph.toml
petiglyph use-project my-font build
petiglyph sample --manifest my-font/petiglyph.toml
petiglyph use-project my-font show-sample
petiglyph glyph create --input logo.png --manifest my-font/petiglyph.toml
petiglyph use-project my-font create glyph --input logo.png
Consumers parsing JSON should update expected command identifiers and data
objects to the new project-oriented contract.
Distribution And Release Reliability
- Repaired GitHub release archive creation and smoke checks.
- Preserved the expected directory structure in Windows release archives.
- Installed FFmpeg for release smoke tests with hardened Windows fallback
handling. - Improved npm and PyPI bootstrap publication using scoped tokens or trusted
publishing. - Added npm trusted-publishing setup support.
- Made TestPyPI publication tolerate files already uploaded during retries.
- Added AUR publication helpers and packaging-only
pkgrelupdate support. - Aligned AUR package metadata and dependencies.
Supported Media
- Static imports: PNG, JPEG, WebP, BMP, GIF, SVG, and AVIF.
- Animation imports: GIF, MP4, MOV, MKV, WebM, AVI, and M4V.
- AVIF imports are converted to project-local PNG files.
Binaries
Prebuilt GitHub and npm binaries are provided for:
- Linux GNU on x86-64 and ARM64
- Linux musl on x86-64 and ARM64
- macOS on Intel and Apple Silicon
- Windows on x86-64 and ARM64
PyPI provides Linux GNU manylinux, macOS, and Windows wheels plus a source
distribution. Musllinux wheels are not currently published.
The AUR package requires ffmpeg and fontconfig.
macOS and Windows artifacts are unsigned.
v0.1.0
petiglyph
Summary
First public release of petiglyph, a TUI and CLI tool for turning images and videos into custom font glyphs.
Highlights
- TUI-first workflow with matching CLI commands for automation.
- Project-local layout centered on
petiglyph.toml,images/, andbuild/. - Glyph, grid, composition, and animation import flows.
- Build, install, sample, uninstall, and doctor commands for day-to-day font work.
- Per-glyph threshold and invert controls.
- Prebuilt release archives for Linux GNU, Linux musl, macOS, and Windows.
Packaging
- GitHub Releases provide prebuilt archives for x86-64 and ARM64 on Linux, macOS, and Windows.
- npm publishes
petiglyphand platform packages. - PyPI publishes wheels and an sdist.
- The AUR package is published separately.
Notes
ffmpegis required beforepetiglyphstarts.- macOS and Windows binaries are unsigned unless this release notes otherwise.
- This release is intended as the first stable public baseline for the current CLI/TUI contract.