Skip to content

Release v0.0.18 #12

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
awnion merged 2 commits into from
Apr 11, 2026
Merged

Release v0.0.18 #12

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
129e6a7
bump version to 0.0.18 and add release docs
awnion Apr 11, 2026
2a632af
add release notes flow to RELEASING.md
awnion Apr 11, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion VERSION
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1 +1 @@
0.0.17
0.0.18
9 changes: 9 additions & 0 deletions docs/RELEASING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,6 +22,15 @@

No rebuild happens on merge. All artifacts are reused from the pre-release.

## Release notes

The PR body is used as release notes throughout the pipeline:

1. The `prerelease` job takes the PR body and passes it as `--notes` to `gh release create`
2. When the PR is merged, the `release` job reads the body from the pre-release via `gh release view` and copies it into the final release via `--notes-file`

**PR body -> pre-release notes -> release notes.** Write the changelog in the PR description.

## Fork builds

A separate `fork-release.yaml` workflow handles forks. When `private-build-plans.toml` changes on `main` in a forked repo, it automatically builds the font and publishes a `latest` pre-release.
Loading