@databricks-solutions/lakebase-scm-utils 0.2.42 → 0.2.44

package/templates/project/common/.github/workflows/pr.yml

@@ -33,14 +33,25 @@ jobs:
           SCM_UTILS_REF="$(tr -d '[:space:]' < .lakebase/scm-utils-ref 2>/dev/null || true)"
           SCM_UTILS_REF="${SCM_UTILS_REF:-v{{LAKEBASE_SCM_UTILS_VERSION}}}"
           echo "SCM_UTILS_REF=${SCM_UTILS_REF}" >> "$GITHUB_ENV"
-          # Registry-first: version-tag refs install the published tarball from the
-          # npm registry (seconds); branch/SHA refs keep the GitHub source form
-          # (their only source).
+          # Registry-first for version tags, with a GitHub fallback when the registry
+          # cannot serve the tarball yet: a freshly-published version is blocked by
+          # the proxy's same-day security screen for ~24h (a staging merge then fails
+          # on npx ETARGET), and a branch/SHA ref only ever has GitHub. Probe the
+          # tarball URL once and pick the source that actually serves it, so a
+          # same-day publish never stalls CI.
+          SPEC=""
           case "$SCM_UTILS_REF" in
-            v[0-9]*) echo "SCM_UTILS_NPX_PKG=@databricks-solutions/lakebase-scm-utils@${SCM_UTILS_REF#v}" >> "$GITHUB_ENV" ;;
-            [0-9]*)  echo "SCM_UTILS_NPX_PKG=@databricks-solutions/lakebase-scm-utils@${SCM_UTILS_REF}" >> "$GITHUB_ENV" ;;
-            *)       echo "SCM_UTILS_NPX_PKG=github:databricks-solutions/lakebase-scm-utils#${SCM_UTILS_REF}" >> "$GITHUB_ENV" ;;
+            v[0-9]*|[0-9]*) SPEC="@databricks-solutions/lakebase-scm-utils@${SCM_UTILS_REF#v}" ;;
           esac
+          if [ -n "$SPEC" ]; then
+            TARBALL_URL="$(npm view "${SPEC}" dist.tarball 2>/dev/null || true)"
+            if [ -z "$TARBALL_URL" ] || ! curl -fsSI --max-time 15 "$TARBALL_URL" >/dev/null 2>&1; then
+              echo "resolve-substrate: registry cannot serve ${SPEC} yet (same-day publish screen); falling back to GitHub."
+              SPEC=""
+            fi
+          fi
+          [ -z "$SPEC" ] && SPEC="github:databricks-solutions/lakebase-scm-utils#${SCM_UTILS_REF}"
+          echo "SCM_UTILS_NPX_PKG=${SPEC}" >> "$GITHUB_ENV"
 
       - name: Detect project language
         id: detect-lang

package/templates/project/common/scripts/run-tests.sh

@@ -176,6 +176,16 @@ if [ "$#" -eq 0 ] && [ -f "$REPO_ROOT/client/package.json" ]; then
       ( cd "$REPO_ROOT/client" && npm install --include=dev )
     fi
   fi
+  # Strict typecheck BEFORE the tests, matching CI. CI builds the client with
+  # `tsc --noEmit && vite build` (strict), but the local test lanes run vitest +
+  # Playwright against the Vite dev server, which does NOT strict-typecheck the whole
+  # app — so a cross-story type regression (a later story making a field REQUIRED,
+  # breaking an earlier story's construction of that type) passed the local honest-GREEN
+  # + deploy feature-verify and was caught ONLY by CI, after promote. Run the SAME strict
+  # typecheck here so local GREEN matches CI. `--if-present` no-ops on an older scaffold
+  # with no `typecheck` script; a type error fails the run (set -e), exactly like a test.
+  echo "Running client strict typecheck (tsc --noEmit, matching CI's build)..."
+  ( cd "$REPO_ROOT/client" && npm run typecheck --if-present )
   echo "Running client unit tests (Vitest)..."
   ( cd "$REPO_ROOT/client" && npm test )
 fi

package/templates/project/python/tests/conftest.py

@@ -41,9 +41,16 @@ def _restore_migration_head_after_each_test():
 
         from alembic import command
         from alembic.config import Config
+        from alembic.util.exc import CommandError
+        from sqlalchemy.exc import OperationalError
 
         ini = str(Path(__file__).resolve().parent.parent / "alembic.ini")
         command.upgrade(Config(ini), "head")
-    except Exception:
-        # Best-effort isolation; never fail a test on teardown restoration.
-        pass
+    except (CommandError, OperationalError) as exc:
+        # Best-effort isolation, but never SILENT and never an umbrella swallow:
+        # surface a restore failure instead of hiding it (a broken migration must
+        # be visible, not masked as routine teardown noise). CommandError wraps
+        # alembic's own failures; OperationalError covers DBAPI/connection errors.
+        # Everything else (a real schema error) propagates and fails loudly, which
+        # is the correct behavior for a genuinely broken restore.
+        print(f"WARNING: migration-head restore failed during teardown: {exc}")