@crossdelta/platform-sdk 0.25.2 → 0.25.4

package/bin/templates/workspace/.github/actions/prepare-build-context/action.yml

@@ -71,10 +71,15 @@ runs:
               continue
             fi
             
-            # Use npm version if local version isn't published yet (race with publish workflow)
+            # Use npm version if local version isn't published yet (race with publish workflow).
+            # The manifest is not enough: it lists a version minutes before the tarball is on
+            # the CDN, and bun install then gets a 404 for the tarball — and hangs on it instead
+            # of failing (2026-09-17, platform-sdk 0.25.2, 36 minutes until the run was cancelled).
+            # So the tarball itself has to answer before the local version is trusted.
             npm_version=$(npm view "$pkg_name" version 2>/dev/null || echo "")
-            if [ -n "$npm_version" ] && ! npm view "$pkg_name@$pkg_version" version >/dev/null 2>&1; then
-              echo "  $pkg_name@$pkg_version not on npm yet, using ^$npm_version"
+            tarball=$(npm view "$pkg_name@$pkg_version" dist.tarball 2>/dev/null || echo "")
+            if [ -n "$npm_version" ] && { [ -z "$tarball" ] || ! curl -sfIL --max-time 20 "$tarball" >/dev/null; }; then
+              echo "  $pkg_name@$pkg_version not downloadable from npm yet, using ^$npm_version"
               pkg_version="$npm_version"
             fi
             
@@ -143,7 +148,11 @@ runs:
           echo "Regenerating bun.lock for modified workspace..."
           cp bun.lock bun.lock.bak
           set +e
-          NPM_TOKEN="${{ inputs.npm-token }}" bun install --no-progress 2>&1 | tee /tmp/bun-install.log; INSTALL_EXIT=${PIPESTATUS[0]}
+          # Bounded: bun install has hung indefinitely after a 404 on a tarball (see above), and an
+          # unbounded hang here holds the job until the runner's 6-hour limit. A timeout turns it
+          # into the failure path below, which restores the original lockfile.
+          NPM_TOKEN="${{ inputs.npm-token }}" timeout 300 bun install --no-progress 2>&1 | tee /tmp/bun-install.log; INSTALL_EXIT=${PIPESTATUS[0]}
+          [ "$INSTALL_EXIT" -eq 124 ] && echo "::warning::bun install timed out after 300 s"
           set -e
           if [ ! -f bun.lock ] || [ ! -s bun.lock ]; then
             echo "::warning::bun install (exit $INSTALL_EXIT) produced no valid bun.lock — restoring original so Docker COPY does not fail"

package/bin/templates/workspace/.github/workflows/build-and-deploy.yml.hbs

@@ -270,11 +270,16 @@ jobs:
       group: deploy-job-$\{{ github.ref }}
       cancel-in-progress: false
     needs: [gate, build, prepare-scopes]
+    # `always()` only so an infrastructure-only run (build skipped) still deploys. A cancelled
+    # build must not: its scopes carry no marker, and the marker-less fallback below would then
+    # deploy the newest checksum image GHCR holds for them — an older commit, possibly a stage
+    # build. That happened on 2026-09-17 (run 35254568199): four app builds cancelled, deploy
+    # went ahead on the previous commit's images.
     if: |
       always() &&
       needs.gate.outputs.proceed == 'true' &&
       needs.prepare-scopes.result == 'success' &&
-      needs.build.result != 'failure' &&
+      (needs.build.result == 'success' || needs.build.result == 'skipped') &&
       (needs.prepare-scopes.outputs.scope_count != '0' || needs.prepare-scopes.outputs.infrastructure_changed == 'true')
     name: 🌍 Deploy ($\{{ github.event.inputs.environment || 'stage' }})
     environment: $\{{ github.event.inputs.environment || 'stage' }}
@@ -360,9 +365,14 @@ jobs:
         run: |
           bunx turbo run build --filter=@crossdelta/infrastructure --filter={{scope}}/contracts
 
+      # 15, not 5: a node-pool resize alone takes 3-6 minutes (provision the droplet, join, Ready)
+      # and the provider waits for the cluster to report `running` again — on top of the service
+      # rollouts. Five minutes was not enough on 2026-09-22, and a timeout kills the process
+      # mid-update: DigitalOcean finishes the resize server-side anyway, while Pulumi never writes
+      # the result back and leaves a stack lock and a pending operation behind.
       - name: Pulumi up
         uses: pulumi/actions@v7
-        timeout-minutes: 5
+        timeout-minutes: 15
         with:
           command: up
           suppress-progress: true

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@crossdelta/platform-sdk",
-  "version": "0.25.2",
+  "version": "0.25.4",
   "description": "Platform toolkit for event-driven microservices — keeping code and infrastructure in lockstep.",
   "keywords": [
     "cli",