Commit 971bdb3e80
971bdb3e8073965ebbb1924864b0442cd3d8dc95
parent: b80180e77e
Unregistered key
cmc <hello@cleberg.net> · 2026-07-15 22:42 UTC
committer: <noreply@github.com>
chore: drop the release workflow (#3)
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.
Layout: unified · split
.github/workflows/release.yml
deleted
−23
| @@ -1,23 +0,0 @@ |
| 1 | name: Release |
| |
| 2 | |
| |
| 3 | on: |
| |
| 4 | push: |
| |
| 5 | tags: |
| |
| 6 | - 'v*' |
| |
| 7 | |
| |
| 8 | permissions: |
| |
| 9 | contents: write |
| |
| 10 | |
| |
| 11 | jobs: |
| |
| 12 | release: |
| |
| 13 | runs-on: ubuntu-latest |
| |
| 14 | steps: |
| |
| 15 | - uses: actions/checkout@v7 |
| |
| 16 | - name: Create Release |
| |
| 17 | uses: elgohr/Github-Release-Action@v5 |
| |
| 18 | env: |
| |
| 19 | GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} |
| |
| 20 | with: |
| |
| 21 | title: Release ${{ github.ref }} |
| |
| 22 | tag: ${{ github.ref }} |
| |
| 23 | prerelease: false |
| |