From 5737aa6afec165581db81093b63265a156f6f93d Mon Sep 17 00:00:00 2001 From: Christian Cleberg Date: Wed, 15 Jul 2026 17:36:19 -0500 Subject: [PATCH] chore: drop the release workflow The workflow turned a v* tag into an empty GitHub release. For a library with no binaries to attach, that is exactly what the Releases button in the UI does, so it earned nothing and had never once succeeded: the v0.3.1 runs were denied by a read-only GITHUB_TOKEN, and the v0.3.2 run raced a release published by hand and got a 422. Releases are cut in the UI, which also creates the tag. Go resolves tags through the module proxy, so nothing about publishing depends on this. Worth knowing if it ever comes back: it passed github.ref, so the title rendered as "Release refs/tags/v0.3.2". It wants github.ref_name. --- .github/workflows/release.yml | 23 ----------------------- 1 file changed, 23 deletions(-) delete mode 100644 .github/workflows/release.yml diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml deleted file mode 100644 index 7958b45..0000000 --- a/.github/workflows/release.yml +++ /dev/null @@ -1,23 +0,0 @@ -name: Release - -on: - push: - tags: - - 'v*' - -permissions: - contents: write - -jobs: - release: - runs-on: ubuntu-latest - steps: - - uses: actions/checkout@v7 - - name: Create Release - uses: elgohr/Github-Release-Action@v5 - env: - GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} - with: - title: Release ${{ github.ref }} - tag: ${{ github.ref }} - prerelease: false