gowalk-cicd 1.0.38 → 1.0.39

package/CLAUDE.md

@@ -101,6 +101,9 @@ node /path/to/gowalk-cicd/bin/cli.mjs
 - Backend runtime credentials use the single encrypted `BACKEND_RUNTIME_ENV`
   secret. The action writes it to host-side `.runtime.env` with mode 0600 and
   supplies it to Compose after the generated `.env`; never print its content.
+- The mobile workflow's feature-branch-only `backend-preview` job bootstraps a
+  new app before GitHub registers `deploy-backend.yml` on the default branch.
+  Default-branch deploys continue through the separate backend workflow.
 - The Android action serves two build systems. `android_config.project_kind()`
   is the only place that decides which; every downstream step branches on the
   `project_kind` output rather than re-sniffing the repo. Flutter wins the tie

package/README.md

@@ -72,6 +72,11 @@ Requirements on the consumer repo:
 The action directory is canonical here (like the iOS/Android actions): edit it in
 `backend-action/`, never in a consumer's vendored copy.
 
+For a new app whose separate backend workflow is not registered on the default
+branch yet, manually dispatching **Mobile Deploy** on the feature branch runs
+the same backend action as a `backend-preview` job. The job is feature-branch
+only; normal default-branch backend deploys remain in `deploy-backend.yml`.
+
 ## Android credentials
 
 Place these files under `creds/`:

package/action/.daemux-version

@@ -1 +1 @@
-1.0.38
+1.0.39

package/android-action/.daemux-version

@@ -1 +1 @@
-1.0.38
+1.0.39

package/backend-action/.daemux-version

@@ -1 +1 @@
-1.0.38
+1.0.39

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "gowalk-cicd",
-  "version": "1.0.38",
+  "version": "1.0.39",
   "description": "Zero-config GitHub Actions delivery for iOS TestFlight and Android Google Play.",
   "type": "module",
   "bin": {

package/templates/deploy.yml

@@ -397,3 +397,35 @@ jobs:
           uploaded without being submitted. Open Play Console for \
           ${{ steps.android.outputs.package-name }} and press 'Send changes for review' on the \
           Publishing overview page. This is normal after a policy rejection."
+
+  # GitHub only registers a newly added workflow after it reaches the default
+  # branch. A brand-new app's feature branch therefore cannot dispatch the
+  # separate Backend Deploy workflow yet. Reuse this already-registered mobile
+  # workflow for the first feature-branch deploy; default-branch pushes keep
+  # using deploy-backend.yml and never run this job twice.
+  backend-preview:
+    name: Backend Deploy
+    if: >-
+      ${{ github.event_name == 'workflow_dispatch'
+          && github.ref_name != github.event.repository.default_branch }}
+    runs-on: ubuntu-latest
+    timeout-minutes: 30
+    steps:
+      - uses: actions/checkout@df4cb1c069e1874edd31b4311f1884172cec0e10 # v6
+      - id: dir
+        shell: bash
+        run: |
+          if [ -f backend/docker-compose.yml ]; then echo "path=backend" >> "$GITHUB_OUTPUT"
+          elif [ -f server/docker-compose.yml ]; then echo "path=server" >> "$GITHUB_OUTPUT"
+          else echo "path=" >> "$GITHUB_OUTPUT"; fi
+      - name: Deploy backend from feature branch
+        if: ${{ steps.dir.outputs.path != '' }}
+        uses: ./.github/actions/backend-app
+        with:
+          ssh-key: ${{ secrets.BACKEND_DEPLOY_SSH_KEY }}
+          host: ${{ vars.BACKEND_DEPLOY_HOST || '138.197.36.107' }}
+          app-name: ${{ vars.BACKEND_APP_NAME || github.event.repository.name }}
+          api-domain: ${{ vars.BACKEND_API_DOMAIN }}
+          backend-dir: ${{ steps.dir.outputs.path }}
+          health-path: ${{ vars.BACKEND_HEALTH_PATH || '/health' }}
+          runtime-env: ${{ secrets.BACKEND_RUNTIME_ENV }}