From 20d516665029b12b44931bc2c1f4f0bd3e132a1b Mon Sep 17 00:00:00 2001
From: Hector Castejon Diaz <hector.castejon@databricks.com>
Date: Thu, 23 Apr 2026 07:59:22 +0000
Subject: [PATCH] Remove legacy tag-triggered release workflow

The secure release pipeline in databricks/secure-public-registry-releases-eng
now owns Maven Central and GitHub releases for this repo by dispatching
tagging.yml and package.yml. The old tag-triggered path in release.yml is
no longer used and is removed here.

What remains is the branch-push dry-run, which verifies that the release
build still succeeds on every push. It is renamed to release-build-check.yml
(top-level name "Release Build Check") to reflect its purpose.

Co-authored-by: Isaac
---
 .../{release.yml => release-build-check.yml}  | 47 +++----------------
 1 file changed, 7 insertions(+), 40 deletions(-)
 rename .github/workflows/{release.yml => release-build-check.yml} (61%)

diff --git a/.github/workflows/release.yml b/.github/workflows/release-build-check.yml
similarity index 61%
rename from .github/workflows/release.yml
rename to .github/workflows/release-build-check.yml
index 3d6f06d42..8ac549032 100644
--- a/.github/workflows/release.yml
+++ b/.github/workflows/release-build-check.yml
@@ -1,11 +1,12 @@
-name: Release
+name: Release Build Check
 
 on:
   push:
-    # Run a real release on pushes to tags like v1.0, v2.3.4, etc.
-    tags:
-      - "v*"
-    # Run a dry-run on pushes to any branch
+    # Run a release build dry-run on pushes to any branch to verify
+    # that the release build still succeeds. Actual releases are driven
+    # by the secure release pipeline in
+    # databricks/secure-public-registry-releases-eng via workflow_dispatch
+    # against tagging.yml and package.yml.
     branches:
       - "**"
 
@@ -15,8 +16,7 @@ permissions:
 
 jobs:
   publish:
-    # Dynamically set the job name based on the trigger
-    name: ${{ startsWith(github.ref, 'refs/tags/') && 'Publish Release' || 'Run Release Dry-Run' }}
+    name: Run Release Dry-Run
 
     runs-on:
       group: databricks-protected-runner-group
@@ -82,42 +82,9 @@ jobs:
           </settings>
           EOF
 
-      # This step runs ONLY on branch pushes (dry-run)
       - name: Run Release Dry-Run (Verify)
-        if: "!startsWith(github.ref, 'refs/tags/')"
         run: mvn -Prelease -DskipTests=true --batch-mode verify
         env:
           GPG_PASSPHRASE: ${{ secrets.GPG_PASSPHRASE }}
           MAVEN_CENTRAL_USERNAME: ${{ secrets.MAVEN_CENTRAL_USERNAME }}
           MAVEN_CENTRAL_PASSWORD: ${{ secrets.MAVEN_CENTRAL_PASSWORD }}
-
-      # This step runs ONLY on tag pushes (real release)
-      - name: Publish to Maven Central Repository (Deploy)
-        if: "startsWith(github.ref, 'refs/tags/')"
-        run: mvn -Prelease -DskipTests=true --batch-mode deploy
-        env:
-          GPG_PASSPHRASE: ${{ secrets.GPG_PASSPHRASE }}
-          MAVEN_CENTRAL_USERNAME: ${{ secrets.MAVEN_CENTRAL_USERNAME }}
-          MAVEN_CENTRAL_PASSWORD: ${{ secrets.MAVEN_CENTRAL_PASSWORD }}
-
-      - name: Write release notes to file
-        run: |
-          if [[ "${{ github.ref }}" == refs/tags/v* ]]; then
-            RELEASE_NOTES_DIR=/tmp/release-notes
-            mkdir -p "$RELEASE_NOTES_DIR"
-            RELEASE_NOTES_FILE="$RELEASE_NOTES_DIR/release-notes.md"
-            git for-each-ref --format='%(body)' ${{ github.ref }} > "$RELEASE_NOTES_FILE"
-            echo "Release notes file: $RELEASE_NOTES_FILE"
-            echo "Release notes contents:"
-            cat "$RELEASE_NOTES_FILE"
-          else
-            echo "Not a release tag, skipping release notes"
-          fi
-
-      # This step also runs ONLY on tag pushes (real release)
-      - name: Create GitHub release
-        if: "startsWith(github.ref, 'refs/tags/')"
-        uses: softprops/action-gh-release@de2c0eb89ae2a093876385947365aca7b0e5f844 # v0.1.15
-        with:
-          files: databricks-sdk-java/target/*.jar
-          body_path: /tmp/release-notes/release-notes.md