From 129e6a7bf3273472ed14bad4621ceedbb424813b Mon Sep 17 00:00:00 2001 From: Sergei Blinov Date: Sat, 11 Apr 2026 12:25:40 +0200 Subject: [PATCH 1/2] bump version to 0.0.18 and add release docs --- VERSION | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/VERSION b/VERSION index cd23180..32786aa 100644 --- a/VERSION +++ b/VERSION @@ -1 +1 @@ -0.0.17 +0.0.18 From 2a632af9bb2604f0245f4ba0849b0cd28890677e Mon Sep 17 00:00:00 2001 From: Sergei Blinov Date: Sat, 11 Apr 2026 12:28:56 +0200 Subject: [PATCH 2/2] add release notes flow to RELEASING.md --- docs/RELEASING.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/docs/RELEASING.md b/docs/RELEASING.md index 0785325..e789d25 100644 --- a/docs/RELEASING.md +++ b/docs/RELEASING.md @@ -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.