fix: release workflow to use release.md as body instead of tag annotation to avoid stripping markdown headings

Author: wizpizz

.github/workflows/release_build.yml

@@ -50,7 +50,7 @@ jobs:
         if-no-files-found: error
 
     # Optional: Upload to GitHub Release (if triggered by tag)
-    - name: Fetch tag annotation
+    - name: Fetch tag annotation and release notes
       if: startsWith(github.ref, 'refs/tags/')
       id: tag_data
       run: |
@@ -60,12 +60,25 @@ jobs:
         # Extract tag annotation message
         TAG_MESSAGE=$(git tag -l --format='%(contents)' ${{ github.ref_name }})
         
-        # Output the tag message for use in releases
+        # Also read the release.md file if it exists
+        if [ -f "docs/release.md" ]; then
+          RELEASE_NOTES=$(cat docs/release.md)
+        else
+          RELEASE_NOTES="$TAG_MESSAGE"
+        fi
+        
+        # Output both for use in releases
         {
           echo 'annotation<<EOF'
           echo "$TAG_MESSAGE"
           echo 'EOF'
         } >> $GITHUB_OUTPUT
+        
+        {
+          echo 'release_notes<<EOF'
+          echo "$RELEASE_NOTES"
+          echo 'EOF'
+        } >> $GITHUB_OUTPUT
 
     # Replaced actions/create-release and actions/upload-release-asset
     - name: Create GitHub Release
@@ -75,9 +88,9 @@ jobs:
         # Use the tag name from the Git ref
         tag: ${{ github.ref_name }}
         # Use the tag name for the release name
-        name: Release ${{ github.ref_name }}
-        # Use the tag annotation message as the release body
-        body: ${{ steps.tag_data.outputs.annotation }}
+        name: v${{ github.ref_name }}
+        # Use the release.md content as the release body (preferred) or fallback to tag annotation
+        body: ${{ steps.tag_data.outputs.release_notes }}
         # Path to the artifact to upload
         artifacts: app/build/outputs/apk/release/app-release.apk
         # The action defaults to using github.token, which is fine with permissions set
@@ -109,13 +122,13 @@ jobs:
         cat > release_body.md << 'EOF'
         **Synced from main repo release: ${{ github.ref_name }}**
         
-        ${{ steps.tag_data.outputs.annotation }}
+        ${{ steps.tag_data.outputs.release_notes }}
         EOF
         
         # Create release using GitHub CLI
         gh release create "${{ steps.version_info.outputs.xposed_tag }}" \
           --repo "Xposed-Modules-Repo/com.wizpizz.onepluspluslauncher" \
-          --title "Release ${{ steps.version_info.outputs.xposed_tag }}" \
+          --title "v${{ github.ref_name }}" \
           --notes-file "release_body.md" \
           "app/build/outputs/apk/release/app-release.apk" || \
         # If release exists, upload to existing release

docs/release.md

@@ -19,10 +19,12 @@ If you are using an older version of the launcher, please use an older release,
 * Misc:
     * Several UI improvements.
 
+[Full Changelog](https://github.com/wizpizz/OnePlusPlusLauncher/compare/v1.1.0...v1.2.0)
+
 ## ⬇️ Installation
 
 1. Make sure your device is rooted and you have LSPosed installed.
-2. Download the latest release APK from the assets section below or simply [click here](https://github.com/Xposed-Modules-Repo/com.wizpizz.onepluspluslauncher/releases/download/v1.2.0/app-release.apk)
+2. Download the latest release APK from the assets section below or simply [click here](https://github.com/Xposed-Modules-Repo/com.wizpizz.onepluspluslauncher/releases/download/3-1.2.0/app-release.apk)
 3. Install the APK on your device.
 4. Enable the module in the LSPosed manager and make sure System Launcher is enabled in the scope settings.
 5. Restart System Launcher.