fix(ci): use heredoc delimiter for multi-line commit messages in GITHUB_OUTPUT

Multi-line commit messages (with body/bullet points) broke the
release workflows because 'echo "message=$COMMIT_MSG"' passes
each line as a separate file command. Lines starting with '- '
trigger 'Invalid format' errors in GitHub Actions.

Fix: use heredoc syntax (message<<EOF / EOF) which safely handles
multi-line values in $GITHUB_OUTPUT.

Author: hectoruch

.github/workflows/release-beta.yml

@@ -137,9 +137,10 @@ jobs:
       - name: Get latest commit message
         id: commit
         run: |
-          COMMIT_MSG=$(git log -1 --pretty=%B)
-          echo "message=$COMMIT_MSG" >> $GITHUB_OUTPUT
-          echo "Commit message: $COMMIT_MSG"
+          echo "message<<EOF" >> $GITHUB_OUTPUT
+          git log -1 --pretty=%B >> $GITHUB_OUTPUT
+          echo "EOF" >> $GITHUB_OUTPUT
+          echo "Commit message: $(git log -1 --pretty=format:"%s")"
 
       - name: Create beta changeset
         run: |

.github/workflows/release-canary.yml

@@ -80,7 +80,7 @@ jobs:
         id: detect
         run: |
           BRANCH_NAME="${{ github.ref_name }}"
-          COMMIT_MSG=$(git log -1 --pretty=%B)
+          COMMIT_MSG=$(git log -1 --pretty=format:"%s")
 
           echo "Branch: $BRANCH_NAME"
           echo "Commit: $COMMIT_MSG"
@@ -142,10 +142,11 @@ jobs:
       - name: Get commit info
         id: commit
         run: |
-          COMMIT_MSG=$(git log -1 --pretty=%B)
           COMMIT_SHA=$(git rev-parse --short HEAD)
 
-          echo "message=$COMMIT_MSG" >> $GITHUB_OUTPUT
+          echo "message<<EOF" >> $GITHUB_OUTPUT
+          git log -1 --pretty=%B >> $GITHUB_OUTPUT
+          echo "EOF" >> $GITHUB_OUTPUT
           echo "sha=$COMMIT_SHA" >> $GITHUB_OUTPUT
 
       - name: Create canary changeset