Commit graph

7 commits

Author SHA1 Message Date
patriceckhart
b29c6e7e2d chore: drop homebrew distribution
The homebrew-tap repo was never created and maintaining a
separate tap for a small tool adds release-pipeline surface
for no real benefit (install.sh and go install cover macos
already). Removed from:

- README.md install section
- .goreleaser.yaml brews block + the release header that
  advertised the brew one-liner
- .github/workflows/release.yml env export for
  HOMEBREW_TAP_TOKEN (no longer consumed)

No other surfaces referenced it. Installers (install.sh /
install.ps1) never mentioned brew.
2026-04-20 14:17:58 +02:00
patriceckhart
8a13141ace release: use rare opt-out token that prose won't match
the previous guard string kept matching because i literally mentioned
it in my own commit messages when documenting the feature. switched
to a form with an equals sign that will never appear in ordinary
english.
2026-04-18 11:23:02 +02:00
patriceckhart
4d847ec633 release: remove debug job, gate brew upload on HOMEBREW_TAP_TOKEN
- debug job served its purpose (proved workflow_run fires correctly)
  and is gone
- restore the [skip-release] guard
- brews.skip_upload is now a go-template that evaluates to true when
  HOMEBREW_TAP_TOKEN is empty, so tag pushes before the tap is
  created don't fail the whole release (v0.0.1 cut fine but the
  goreleaser exit code was 1 because the brew step 401'd)
2026-04-18 11:21:32 +02:00
patriceckhart
75aa6d4771 ci: add debug step to dump workflow_run payload
the release job kept getting skipped even though the if-expression
should have evaluated true. adding a diagnostic job (no if-filter)
that prints github.event.workflow_run so we can see what fields
are actually populated on the webhook payload at eval time.
removing the [skip-release] guard temporarily to reduce variables.
2026-04-18 11:17:10 +02:00
patriceckhart
f0014f10fa release: rename skip directive to [skip-release] (hyphen)
the previous [skip release] (space) matched my own commit message
that literally described the feature, which caused the first green
ci run to skip the release instead of cutting v0.0.1. hyphenated
form is much less likely to show up in ordinary prose.

also switch the job-level if from folded-scalar yaml to an inline
${{ }} expression for robustness.
2026-04-18 11:15:28 +02:00
patriceckhart
63547d43ba release: auto-tag and publish on every green ci run
- release.yml now triggers on workflow_run of ci (completed+success),
  not on bare push, so we never publish binaries of broken code
- checks out github.event.workflow_run.head_sha, computes the next
  vX.Y.Z by bumping the patch of the newest existing tag (starts at
  v0.0.1), pushes the tag, runs goreleaser
- supports [skip release] in the commit message for docs/ci-only
  commits that shouldn't cut a version
2026-04-18 11:13:39 +02:00
patriceckhart
4712f5e0e3 add installation process and github workflow 2026-04-18 10:50:02 +02:00