Merge branch 'PRO' of https://git.freetimelab.es/FreeTLab/pluriwave into PRO

ci: name build artifacts by branch and version code [version set]
Every build of a given semver was published as `pluriwave-v1.3.0.aab` into the same folder, so main and PRO overwrote each other and three different builds became indistinguishable once downloaded — the browser saves them as "(1)", "(2)" and the version code is only visible by unzipping the bundle. That cost two rejected uploads to Play Console for reusing a version code. Artifacts are now `pluriwave-<branch>-v<semver>+<build>.<ext>", which identifies itself weeks later and outside this repo.
2026-08-28 23:52:27 +02:00 · 2026-08-28 23:52:16 +02:00 · 2026-08-28 23:40:45 +02:00 · 2026-08-28 23:38:15 +02:00 · 2026-08-28 19:59:13 +02:00
2 changed files with 18 additions and 5 deletions
@@ -237,11 +237,24 @@ jobs:
      - name: Build AAB release
        run: flutter build appbundle --release

+      # El nombre lleva RAMA y CÓDIGO DE VERSIÓN, no solo el semver.
+      #
+      # Antes, cada build de 1.3.0 se llamaba `pluriwave-v1.3.0.aab` y caía en
+      # la misma carpeta, así que main y PRO se pisaban y tres builds distintos
+      # eran indistinguibles una vez descargados: el navegador los guarda como
+      # "(1)", "(2)"... y ya no se sabe cuál es cuál. Eso costó subir a Play
+      # Console un código de versión ya usado, dos veces.
+      #
+      # Con `pluriwave-PRO-v1.3.0+156.aab` el archivo se identifica solo,
+      # incluso semanas después y fuera de este repo.
      - name: Publicar en ftl-builds (Zimaboard)
        run: |
          VERSION="${{ steps.version.outputs.version }}"
-          APK_NOMBRE="pluriwave-v${VERSION}.apk"
-          AAB_NOMBRE="pluriwave-v${VERSION}.aab"
+          BUILD_NUMBER="${{ steps.version.outputs.build_number }}"
+          BRANCH="${CURRENT_REF#refs/heads/}"
+          ETIQUETA="${BRANCH}-v${VERSION}+${BUILD_NUMBER}"
+          APK_NOMBRE="pluriwave-${ETIQUETA}.apk"
+          AAB_NOMBRE="pluriwave-${ETIQUETA}.aab"
          DESTINO="/opt/ftl-builds/builds/pluriwave/v${VERSION}"
          SSH_KEY="/Users/freetlab/.openclaw/workspace/.secure/zimaboard_ed25519"

@@ -252,8 +265,8 @@ jobs:
          scp -i "$SSH_KEY" -o StrictHostKeyChecking=no \
            build/app/outputs/bundle/release/app-release.aab \
            "ShanaiaBot@192.168.0.33:${DESTINO}/${AAB_NOMBRE}"
-          echo "✅ APK: builds.freetimelab.es → pluriwave → v${VERSION}"
-          echo "✅ AAB: builds.freetimelab.es → pluriwave → v${VERSION}"
+          echo "✅ APK: builds.freetimelab.es → pluriwave → v${VERSION} → ${APK_NOMBRE}"
+          echo "✅ AAB: builds.freetimelab.es → pluriwave → v${VERSION} → ${AAB_NOMBRE}"

      - name: Preparar credenciales de Google Play
        if: ${{ gitea.ref == 'refs/heads/PRO' }}
@@ -1,7 +1,7 @@
 name: pluriwave
 description: "Radio mundial con ecualizador, reconocimiento de canciones y UI premium"
 publish_to: 'none'
-version: 1.3.2+155
+version: 1.3.0+156

 environment:
  sdk: ^3.7.0
Author	SHA1	Message	Date
FreeTLab	98b24d84cd	Merge branch 'PRO' of https://git.freetimelab.es/FreeTLab/pluriwave into PRO Build & Deploy PluriWave / Análisis de código (push) Successful in 25s Details Build & Deploy PluriWave / Build APK + AAB release (push) Failing after 19s Details	2026-08-28 23:52:27 +02:00
FreeTLab	72c5777508	ci: name build artifacts by branch and version code [version set] Every build of a given semver was published as `pluriwave-v1.3.0.aab` into the same folder, so main and PRO overwrote each other and three different builds became indistinguishable once downloaded — the browser saves them as "(1)", "(2)" and the version code is only visible by unzipping the bundle. That cost two rejected uploads to Play Console for reusing a version code. Artifacts are now `pluriwave-<branch>-v<semver>+<build>.<ext>", which identifies itself weeks later and outside this repo.	2026-08-28 23:52:16 +02:00
ShanaiaBot	b69041f32a	chore: bump version to 1.3.0+156 [ci skip]	2026-08-28 23:40:45 +02:00
FreeTLab	9681a47e83	merge: alarm-import recovery, dismissible paywall and complete config export [version set] Build & Deploy PluriWave / Análisis de código (push) Successful in 25s Details Build & Deploy PluriWave / Build APK + AAB release (push) Failing after 2m1s Details Same three fixes already merged to main (`e57f7bb`, `a2bed18`, `4ca2813`): alarms actually come back after a backup import and get re-scheduled natively, the premium sheet can be dismissed, and the equalizer on/off toggle finally travels with the backup. [version set] keeps the 1.3.0 release name; CI advances the build number. # Conflicts: # pubspec.yaml	2026-08-28 23:38:15 +02:00
ShanaiaBot	524b8f0035	chore: bump version to 1.3.0+154 [ci skip]	2026-08-28 19:59:13 +02:00