feat: switch to snapshot versions for commits, manual releases for official versions (#1654)

Author: hsluoyz

.github/workflows/default.yml

@@ -38,22 +38,3 @@ jobs:
 
       - name: Run go test bench
         run:  make benchmark
-
-  semantic-release:
-    needs: test
-    runs-on: ubuntu-latest
-    steps:
-      - name: Checkout
-        uses: actions/checkout@v3
-        with:
-          fetch-depth: 0
-      - name: Setup Node.js
-        uses: actions/setup-node@v3
-        with:
-          node-version: 20
-
-      - name: Run semantic-release
-        if: github.repository == 'casbin/casbin' && github.event_name == 'push'
-        run: make release
-        env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

.github/workflows/release.yml

@@ -0,0 +1,41 @@
+name: Release
+
+on:
+  workflow_dispatch:
+    inputs:
+      release_type:
+        description: 'Release type (major, minor, patch)'
+        required: true
+        default: 'patch'
+        type: choice
+        options:
+          - major
+          - minor
+          - patch
+
+jobs:
+  release:
+    runs-on: ubuntu-latest
+    permissions:
+      contents: write
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v3
+        with:
+          fetch-depth: 0
+          token: ${{ secrets.GITHUB_TOKEN }}
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v3
+        with:
+          node-version: 20
+
+      - name: Setup Git
+        run: |
+          git config user.name "github-actions[bot]"
+          git config user.email "github-actions[bot]@users.noreply.github.com"
+
+      - name: Run semantic-release
+        run: npx semantic-release@v19.0.2
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

CONTRIBUTING.md

@@ -33,3 +33,19 @@ Good pull requests (e.g. patches, improvements, new features) are a fantastic he
 Please ask first before embarking on any significant pull request (e.g. implementing new features, refactoring code etc.), otherwise you risk spending a lot of time working on something that the maintainers might not want to merge into the project.
 
 First add an issue to the project to discuss the improvement. Please adhere to the coding conventions used throughout the project. If in doubt, consult the [Effective Go style guide](https://golang.org/doc/effective_go.html).
+
+## Releases
+
+This project uses snapshot versions for development commits. When you merge changes to the master branch, they become available as pseudo-versions that can be referenced using commit hashes.
+
+For users who want to use the latest development version:
+```bash
+go get github.com/casbin/casbin/v3@master
+```
+
+For users who want to use a specific commit:
+```bash
+go get github.com/casbin/casbin/v3@<commit-hash>
+```
+
+Official releases are created manually by maintainers through the [Release workflow](https://github.com/casbin/casbin/actions/workflows/release.yml) in GitHub Actions. This ensures that only stable, well-tested versions receive official version tags.