fix: Use git-cliff for release notes via --release-notes flag

- Add git-cliff install and RELEASE_NOTES.md generation to workflow
- Pass --release-notes=RELEASE_NOTES.md to GoReleaser
- Disable GoReleaser's built-in changelog (git-cliff handles it)
- Update README with pre-release changelog steps

Author: lykinsbd

.github/workflows/release.yml

@@ -39,10 +39,16 @@ jobs:
       - name: Install Syft (for SBOM generation)
         uses: anchore/sbom-action/download-syft@v0.23.0
 
+      - name: Install git-cliff
+        uses: kenji-miyake/setup-git-cliff@v2
+
+      - name: Generate release notes
+        run: git-cliff --latest --strip header -o RELEASE_NOTES.md
+
       - name: Run GoReleaser
         uses: goreleaser/goreleaser-action@v6
         with:
           version: '~> v2'
-          args: release --clean
+          args: release --clean --release-notes=RELEASE_NOTES.md
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

.goreleaser.yml

@@ -59,7 +59,7 @@ snapshot:
   version_template: "{{ .Tag }}"
 
 changelog:
-  sort: asc
+  disable: true
 
 nfpms:
   - id: cisshgo

README.md

@@ -67,16 +67,20 @@ goreleaser release --snapshot --clean --skip=publish
 
 Releases are automated via GitHub Actions. To create a new release:
 
-1. Create and push a tag:
+1. Update the changelog and tag:
 
    ```bash
-   git tag v0.1.2
-   git push origin v0.1.2
+   git-cliff --tag v1.2.3 -o CHANGELOG.md
+   git add CHANGELOG.md
+   git commit -m "docs: update changelog for v1.2.3"
+   git tag -a v1.2.3 -m "v1.2.3"
+   git push origin master v1.2.3
    ```
 
 2. GitHub Actions will automatically:
    - Build binaries for all platforms (linux/darwin/windows, amd64/arm64)
    - Create multi-arch Docker images and push to GitHub Container Registry (ghcr.io)
+   - Generate release notes from git-cliff
    - Generate SBOMs for security compliance
    - Create GitHub Release with binaries, archives, and checksums
    - Build deb/rpm packages