From 876e55a4b957b81867dda5c87fe786f3e3c5c540 Mon Sep 17 00:00:00 2001 From: criseda Date: Thu, 15 Oct 2026 14:10:23 +0100 Subject: [PATCH] Describe the tap's automated cask bump in the release docs The homebrew-tap now runs a daily Bump workflow that opens a PR with the cask's new version and sha256 after each release, so the instructions to bump the cask by hand are out of date. Say that the PR arrives within a day and only needs reviewing and merging. --- .github/workflows/release.yml | 5 +++-- AGENTS.md | 6 ++++-- 2 files changed, 7 insertions(+), 4 deletions(-) diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml index 33a2361..f51f327 100644 --- a/.github/workflows/release.yml +++ b/.github/workflows/release.yml @@ -1,8 +1,9 @@ # Publishes a GitHub release when a version tag (v0.1.0, ...) is pushed: # the ad-hoc signed app as NetScanner-.zip, with that version's # CHANGELOG section as the notes. The Homebrew cask in -# Criseda/homebrew-tap points at this zip; bump its version and sha256 -# (printed in the job log and the release notes) after each release. +# Criseda/homebrew-tap points at this zip. The tap's daily Bump workflow +# notices the new release and opens a PR with the cask's new version and +# sha256 within a day; review and merge it there. name: Release on: diff --git a/AGENTS.md b/AGENTS.md index 067283f..393a0e1 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -233,8 +233,10 @@ Like the engine repo, every user-facing change gets an entry under tag runs `.github/workflows/release.yml`, which checks the tag against `MARKETING_VERSION` and a `## ` CHANGELOG section, builds with `Scripts/package-release.sh` and publishes - `NetScanner-.zip`; then bump the cask's `version` and - `sha256`. The app is ad-hoc signed, not notarized (no paid developer + `NetScanner-.zip`. Within a day the tap's daily Bump + workflow (`.github/workflows/bump.yml`) sees the release through + livecheck and opens a PR with the cask's new `version` and `sha256`; + review and merge it. The app is ad-hoc signed, not notarized (no paid developer account yet), so the official `homebrew/cask` tap will not take it and users allow the first launch in Privacy & Security. - **Developer ID** (later, needs a paid developer account): sign,