refactor: auto release pipeline and readme updated after rebase

Author: serdarozerr

.github/workflows/build.yml

@@ -15,7 +15,7 @@ jobs:
     - name: Set up Go
       uses: actions/setup-go@v6
       with:
-        go-version-file: 'go.mod'
+        go-version-file: go.mod
 
     - name: Storage-CLI Build for Linux
       env:
@@ -53,4 +53,4 @@ jobs:
         path: |
           storage-cli-linux-amd64
           storage-cli-windows-amd64.exe
-        retention-days: 30
+        retention-days: 30

.github/workflows/release.yml .github/workflows/release-auto.yml.github/workflows/release.yml renamed to .github/workflows/release-auto.yml

@@ -1,4 +1,4 @@
-name : Release
+name : Release Auto
 
 on:
   push:

README.md

@@ -133,11 +133,7 @@ Option 2: Release via Draft Release
 - The release will appear immediately on the Releases page. This action will also trigger the *Release Manual* workflow, which will build the artifacts and upload them to the published release once the workflow finishes.
 
 
-## Release
-
-Releases are automatically created for Windows and Linux platforms through the `release.yml` GitHub Actions workflow.
-
-### Automated Release Process
+### Automated Release
 
 When changes are merged into the `main` branch, a new release is automatically triggered. The version number is determined using **semantic versioning** based on conventional commit message prefixes:
 
@@ -156,11 +152,9 @@ When changes are merged into the `main` branch, a new release is automatically t
     - `build:` - Dependabot commits
     - `no conventional commits` - text without specifying any of above
 
-### Manual Release
-
-For manual releases (e.g., major version updates or hotfixes), use the GitHub Actions **workflow_dispatch** trigger with a version bump type selector (patch/minor/major).
+**Note: When the repo becomes more stable, we are gonna merge these 2 release logic.**
 
-### Commit Message Examples
+#### Commit Message Examples
 
 ```bash
 # Major release (v1.2.3 → v2.0.0)