gowalk-cicd 1.0.94 → 1.0.95

package/CLAUDE.md

@@ -52,7 +52,9 @@ vendoring concept are gone.
 ## Publishing
 
 Auto-publish on every push to `main` (the entire repo IS the package). The
-workflow (`.github/workflows/publish.yml`):
+workflow (`.github/workflows/publish.yml`) serializes version selection through
+publication; PR checks use separate cancellable groups. This prevents concurrent
+main runs from choosing the same npm patch version. The workflow:
 
 1. Runs `scripts/auto-version.mjs .` which queries npm for the current
    published version of `gowalk-cicd` and bumps the patch. A first publish
@@ -196,7 +198,9 @@ node /path/to/gowalk-cicd/bin/cli.mjs
   new app before GitHub registers `deploy-backend.yml` on the default branch.
   Default-branch deploys continue through the separate backend workflow.
 - Mobile pushes exclude durable `.factory/progress` records and the separately deployed
-  backend/server/Compose paths. A mixed commit with any native/shared input still builds;
+  backend/server/Compose paths, backend action, docs, marketing, account-recovery scripts,
+  tests and the standard validation/web workflows. Backend action changes trigger only backend
+  deployment; its package version marker alone does not. A mixed commit with any native/shared input still builds;
   explicit workflow dispatch remains available. Keep backend deployment's own path filters
   intact, and do not broadly exclude assets, root build settings or unknown app layouts.
 - Domain-backed backend deploys fail closed on certificate issuance and the

package/README.md

@@ -26,6 +26,20 @@ are unaffected.
 
 Re-run the same command anytime to pull the latest version.
 
+Mobile releases run for changes to the app or its release inputs. Documentation,
+marketing, `tools/recovery/`, tests, `.factory/progress/`, backend-only changes and
+the standard validation/web workflows do not upload another mobile binary. Mixed
+commits still release when they change any app input, including embedded editors,
+assets and build scripts. Backend action changes deploy the backend; updating only
+its `.daemux-version` marker does not. Keep runtime assets outside these excluded
+directories, or customize the filters if your build deliberately includes them.
+
+These filters take effect after updating and committing the consumer workflow
+files with this installer; CI self-update refreshes action directories only.
+Follow an existing push-triggered release before dispatching another one. Manual
+dispatch remains available after an actual release-input or credential repair;
+it bypasses push path filters and can repeat a successful release.
+
 Flutter's optional SDK and pub cache restores have a one-minute timeout per
 download segment. A slow segment becomes a cache miss and normal SDK setup
 continues through the assigned Google proxy; SDK setup errors still fail the

package/action/.daemux-version

@@ -1 +1 @@
-1.0.94
+1.0.95

package/android-action/.daemux-version

@@ -1 +1 @@
-1.0.94
+1.0.95

package/backend-action/.daemux-version

@@ -1 +1 @@
-1.0.94
+1.0.95

package/package.json

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

package/templates/deploy-backend.yml

@@ -11,6 +11,8 @@ on:
       - "server/**"
       - "docker-compose.yml"
       - ".github/workflows/deploy-backend.yml"
+      - ".github/actions/backend-app/**"
+      - "!.github/actions/backend-app/.daemux-version"
   workflow_dispatch:
 
 permissions:

package/templates/deploy.yml

@@ -9,12 +9,22 @@ on:
       # Durable task records and independently deployed backend sources do not
       # change a native binary. Mixed commits still run when any mobile input changes.
       - '.factory/progress/**'
+      - 'docs/**'
+      - 'marketing/**'
+      - 'tools/recovery/**'
+      - 'test/**'
+      - 'tests/**'
+      - 'integration_test/**'
       - 'backend/**'
       - 'server/**'
       - 'docker-compose.yml'
       - '.github/workflows/deploy-backend.yml'
+      - '.github/workflows/deploy-web.yml'
+      - '.github/workflows/flutter-ci.yml'
+      - '.github/workflows/ios-ci.yml'
       - '.github/actions/swift-app/**'
       - '.github/actions/android-app/**'
+      - '.github/actions/backend-app/**'
   workflow_dispatch:
 
 permissions: