git:20260317.6414f98 to git:20260713.8e1e71a

12 added, 3 removed. Audit A to A.

---

name: toastty-publish

description: Use this skill when publishing an existing Toastty release artifact to GitHub Releases, using already-authored release notes and tagging the recorded release commit.

---

# Toastty Publish

Use this workflow when the user already has a built Toastty release artifact and drafted release notes and wants to publish it.

## Core flow

1. Verify that `artifacts/release/<version>-<build>/release-metadata.env`, `ghostty-metadata.env`, `sparkle-metadata.env`, `release-notes.md`, and `Toastty-<version>.dmg` all exist and are non-empty, then read the metadata files.

2. Confirm `RELEASE_SOURCE_COMMIT` is available in the local clone before publishing.

- 3. Confirm the drafted notes at `RELEASE_NOTES_PATH` do not contain leftover `{{placeholder}}` tokens and that the user is satisfied with the existing notes.

+ 3. Confirm the drafted notes at `RELEASE_NOTES_PATH` do not contain leftover

+ `{{placeholder}}` tokens, satisfy the user, and include these exact canonical

+ lines using values from release metadata:

+ ```text

+ - Commit: `<RELEASE_GHOSTTY_COMMIT_SHORT>`

+ - Build flags: `<RELEASE_GHOSTTY_BUILD_FLAGS>`

+ ```

4. Run `scripts/release/publish-github-release.sh --create-tag` to publish a draft by default. Add `--publish` only when the user wants the release to go live immediately and update the Sparkle appcast.

## Important invariants

- Publish must use `artifacts/release/<version>-<build>/release-metadata.env`, not the current `HEAD`, to decide what commit gets tagged.

- Publish must use `artifacts/release/<version>-<build>/sparkle-metadata.env`, not ad-hoc shell values, to decide what gets written to the Sparkle appcast.

- `release-metadata.env` is the source of truth for:

- `RELEASE_SOURCE_COMMIT`

- `RELEASE_NOTES_PATH`

- - `scripts/release/publish-github-release.sh` expects the notes file to exist and be non-empty before publication.

+ - `RELEASE_GHOSTTY_COMMIT_SHORT`

+ - `RELEASE_GHOSTTY_BUILD_FLAGS`

+ - `scripts/release/publish-github-release.sh` expects the notes file to exist, be non-empty, and include exact canonical Ghostty commit and build-flags lines before publication.

- The release directory under `artifacts/release/<version>-<build>/` must remain intact from the earlier build phase.

## Validation

- Before publishing, confirm all three metadata files and the DMG exist and are non-empty.

- Before publishing, confirm `RELEASE_SOURCE_COMMIT` is reachable in the local clone.

- - Before publishing, confirm the notes file exists at `RELEASE_NOTES_PATH` and is non-empty.

+ - Before publishing, confirm the notes file exists at `RELEASE_NOTES_PATH`, is non-empty, and includes the exact canonical Ghostty commit and build-flags lines from release metadata.

- Use `--dry-run` when you want to inspect the derived `git` and `gh` commands before creating the tag or release.