Fix release workflow: upload to extensions platform in-band

The separate upload_to_extension.yml was never triggered for v0.3.2 because
GitHub suppresses workflow events when triggered by GITHUB_TOKEN. Previous
releases worked only because they were draft releases, manually published via
the UI (a human action that does trigger events).

Merge the upload step directly into release.yml after building the release.
This eliminates the cross-workflow event dependency and ensures the upload
always runs immediately after the release is created.

Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>

Author: kolibril13

.github/workflows/release.yml

@@ -31,4 +31,19 @@ jobs:
         run: |
           gh release create ${{ github.ref_name }} --generate-notes *.zip
         env:
-          GITHUB_TOKEN: ${{ github.token }}
+          GITHUB_TOKEN: ${{ github.token }}
+
+      - name: Upload to Extensions Platform
+        env:
+          EXTENSION: typst_importer
+          GITHUB_TOKEN: ${{ github.token }}
+        run: |
+          RELEASE_URL=$(gh release view ${{ github.ref_name }} --json url -q .url)
+          echo "See release notes: ${RELEASE_URL}" > release_notes.txt
+          for zipfile in *.zip; do
+            echo "Uploading $zipfile to Blender Extensions Platform"
+            curl -X POST https://extensions.blender.org/api/v1/extensions/${EXTENSION}/versions/upload/ \
+              -H "Authorization:bearer ${{ secrets.BLENDER_EXTENSIONS_TOKEN }}" \
+              -F "version_file=@${zipfile}" \
+              -F "release_notes=<release_notes.txt"
+          done