Fix releases

Author: Splinter0

.github/workflows/release.yml

@@ -39,3 +39,13 @@ jobs:
           args: release --clean
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+
+      - name: Publish Release
+        uses: softprops/action-gh-release@v2
+        with:
+          tag_name: ${{ github.ref_name }}
+          generate_release_notes: true
+          files: |
+            dist/*.zip
+            dist/*.txt
+          fail_on_unmatched_files: true

.goreleaser.yml

@@ -28,3 +28,6 @@ archives:
 
 changelog:
   use: git
+
+release:
+  disable: true

README.md

@@ -14,17 +14,6 @@ GOOS=windows go build -o relaybox.exe ./cmd/relaybox
 
 You can also find prebuilt binaries on the Releases page.
 
-## Releasing
-
-Tagged releases are automated via [GoReleaser](https://goreleaser.com/). Push a semver tag (for example `v1.2.3`) and GitHub Actions will build the Windows artefact and publish it on GitHub Releases:
-
-```bash
-git tag v1.2.3
-git push origin v1.2.3
-```
-
-The workflow configuration lives in `.github/workflows/release.yml`, while the GoReleaser settings are defined in `.goreleaser.yml`.
-
 ## Why?
 
 NTLM and Kerberos relaying attacks are really powerful, however often times can be impractical, too noisy or too disruptive. This is because at times it is not enough to (or we simply aren't able to):