From e2d1f714faa3807bc42bdb80e9b7330d9868a074 Mon Sep 17 00:00:00 2001 From: stepan_romankov Date: Thu, 21 May 2026 11:17:59 +0200 Subject: [PATCH] docs(CLAUDE.md): release via the Release workflow_dispatch, not manual gh release create The prior instruction told contributors to run `gh release create vX.Y.Z` directly, which bypasses the `go test -race` gate in .github/workflows/release.yml. Point releases at `gh workflow run release.yml -f version=vX.Y.Z` instead. Co-Authored-By: Claude Opus 4.7 --- CLAUDE.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CLAUDE.md b/CLAUDE.md index cddf106..cd06477 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -16,7 +16,7 @@ Samurai is a scoped testing framework for Go with path isolation, inspired by Go ## Git Workflow - **NEVER push directly to master.** Always work through a PR: create a branch, push, `gh pr create`, `gh pr merge`. -- **Use `gh release create` for releases.** Never use manual `git tag` + `git push --tags`. Always create releases via `gh release create vX.Y.Z` so they appear on the GitHub Releases page. +- **Release via the `Release` GitHub Actions workflow (`workflow_dispatch`).** Trigger it with `gh workflow run release.yml -f version=vX.Y.Z` (version must match `v*.*.*`). The workflow gates the release on `go vet` + `go test -race ./...`, then creates the tag and the GitHub Release with `--generate-notes`. NEVER tag or release manually (`git tag`, `gh release create`) — that bypasses the race-test gate. See `.github/workflows/release.yml`. ## Build & Test Commands