build: rename distribution to glyf-core and fix the release workflow - #91
Merged
Conversation
Replace the retired macos-13 runner, build one abi3 wheel per target (x86_64/aarch64 Linux, Intel/Apple Silicon macOS, x86_64 Windows), smoke test each wheel in a clean venv, and attach checksums.txt to the release. Only publish the GitHub Release on tag pushes.
The PyPI name glyf is taken, so the distribution becomes glyf-core; the glyf command and the glyf import are unchanged. Trim the sdist to the package, crate, tests, and top-level metadata. Close out the 0.2.0 changelog entry and open 0.3.0.
Rename docs/release.mdxplain to docs/release.md and document the version locations, the glyf-core distribution name, and the tag-driven release.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Preparation for the first PyPI release.
glyf-core. The bareglyfname on PyPI is held by an unrelated 2022 upload. Theglyfcommand andimport glyfare unchanged; wheels are nowglyf_core-<version>-cp311-abi3-<platform>.whl. Leaves room for a futureglyf-cloudcompanion package.macos-13is retired, which is why thev0.1.0andv0.2.0runs were cancelled and no GitHub Release was ever published. New matrix builds one abi3 wheel per target — x86_64/aarch64 Linux, Intel/Apple Silicon macOS, x86_64 Windows — smoke-tests each in a clean venv, and attacheschecksums.txt. The release job now only runs on tag pushes.pyproject.toml,Cargo.toml,Cargo.lock, andsrc/glyf/__init__.py;CHANGELOG.mdcloses out 0.2.0 (tagged 2026-06-02, never published) and opens 0.3.0.src,tests,crates, and top-level metadata: 206 KB, no docs site, examples,.so, or__pycache__.docs/release.mdxplain→docs/release.md, rewritten for the new flow.Install docs (README, quickstart, existing-dbt-project) still point at the old wheel URLs; those change in a follow-up once the package is actually on PyPI.
Verification
uv run pytest: 114 passeduv build:glyf_core-0.3.0-cp311-abi3-macosx_11_0_arm64.whl+glyf_core-0.3.0.tar.gz; sdist contents inspectedscripts/check-commit-message.sh --range main..HEADpassesv0.3.0tag push.