fix(release): remove version bump automation to avoid branch protection conflicts

The release workflow was trying to auto-update version numbers in files
and push to main, which conflicts with branch protection rules requiring
PRs. This caused releases to fail.

Changes:
- Removed version extraction, checkout, update, and commit steps from workflow
- Changed GNUmakefile VERSION to 'dev' (only used for local sideloading)
- Changed README example to use '~> 1.0' (generic example version)
- Updated release docs to reflect simplified process

GoReleaser automatically uses the git tag version, so tracking versions
in files is unnecessary. The workflow now simply builds and publishes
from the tag without needing to push to main.

Author: Subterrane

.github/workflows/release.yml

@@ -16,44 +16,6 @@ jobs:
         with:
           fetch-depth: 0
 
-      - name: Extract version from tag
-        id: get_version
-        run: |
-          VERSION="${{ github.event.release.tag_name }}"
-          # Remove 'v' prefix if present
-          VERSION="${VERSION#v}"
-          echo "version=$VERSION" >> $GITHUB_OUTPUT
-
-      - name: Checkout main branch
-        run: |
-          # Validate we're releasing from main branch
-          if [ "${{ github.event.release.target_commitish }}" != "main" ]; then
-            echo "Error: Release was not created from 'main' branch (target_commitish=${{ github.event.release.target_commitish }})."
-            exit 1
-          fi
-          # Checkout main branch (release event checks out the tag, putting us in detached HEAD)
-          git checkout main
-          git pull origin main
-
-      - name: Update version in files
-        run: |
-          VERSION="${{ steps.get_version.outputs.version }}"
-          # Update GNUmakefile
-          sed -i -E "s/VERSION=[0-9]+\.[0-9]+\.[0-9]+/VERSION=$VERSION/" GNUmakefile
-          # Update README.md
-          sed -i -E "s/version = \"[0-9]+\.[0-9]+\.[0-9]+\"/version = \"$VERSION\"/" README.md
-          echo "Updated version to $VERSION"
-
-      - name: Commit version changes back to main
-        run: |
-          git config user.name "github-actions[bot]"
-          git config user.email "github-actions[bot]@users.noreply.github.com"
-          git add GNUmakefile README.md
-          # Commit if there are changes (may not be if version files already match)
-          git diff --staged --quiet || git commit -m "chore: bump version to ${{ steps.get_version.outputs.version }}"
-          # Push to main
-          git push origin main
-
       - name: Set up Go
         uses: actions/setup-go@v4
         with:

GNUmakefile

@@ -10,7 +10,9 @@ GO111MODULE=on
 
 PLUGINS_DIR=~/.terraform.d/plugins
 PLUGIN_PATH=onelogin.com/onelogin/onelogin
-VERSION=0.11.0
+# VERSION is only used for local development (make sideload)
+# For releases, GoReleaser uses the git tag version
+VERSION=dev
 
 clean:
 	rm -r ${DIST_DIR}

README.md

@@ -30,7 +30,7 @@ terraform {
   required_providers {
     onelogin = {
       source  = "onelogin/onelogin"
-      version = "0.11.0"
+      version = "~> 1.0"  # Use the latest version from the Terraform Registry
     }
   }
 }
@@ -84,11 +84,9 @@ To create a new release, simply publish a GitHub Release:
 5. Click **"Publish release"**
 
 The Release workflow will automatically:
-- Extract the version from the tag (e.g., `v0.11.1` → `0.11.1`)
-- Update `VERSION` in `GNUmakefile` and the example provider configuration in `README.md`
-- Commit the version changes back to the main branch
-- Build the provider binaries with GoReleaser
-- Attach signed binaries to the GitHub release
+- Build the provider binaries with GoReleaser (using the tag version)
+- Generate checksums and sign them with GPG
+- Attach binaries and checksums to the GitHub release
 - Publish to the Terraform Registry
 
 **That's it!** The entire release process is automated from a single GitHub Release creation.