@pacaf/wizard-ux 3.3.7 → 3.3.9

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pacaf/wizard-ux",
-  "version": "3.3.7",
+  "version": "3.3.9",
   "private": false,
   "type": "module",
   "description": "Browser-based setup wizard for Power Apps Code Apps (parallel to @pacaf/wizard CLI).",
@@ -38,7 +38,7 @@
     "react-dom": "^19.0.0",
     "react-resizable-panels": "^2.1.7",
     "react-router-dom": "^7.1.0",
-    "@pacaf/wizard": "3.3.8"
+    "@pacaf/wizard": "3.3.10"
   },
   "devDependencies": {
     "@types/react": "^19.0.0",

package/server/steps/07-scaffold.mjs

@@ -94,9 +94,17 @@ async function runInstall(log, { stage, label, projectDir, pnpm, mode, packages
   const baseArgs = pnpm
     ? (mode === 'base' ? ['install'] : mode === 'dev' ? ['add', '-D', ...rootFlag, ...packages] : ['add', ...rootFlag, ...packages])
     : (mode === 'base' ? ['install'] : mode === 'dev' ? ['install', '-D', ...packages] : ['install', ...packages]);
+  // `--prefer-online` forces the package manager to revalidate cached registry
+  // metadata (the packument) instead of trusting a warm cache. Without it,
+  // `@pacaf/*@latest` resolves against a stale cached packument and a fresh
+  // scaffold can install a previous @pacaf release even though a newer one is
+  // published (the "Already up to date" trap). This is the single guarantee
+  // that every new repo always picks up the latest published capabilities.
+  // See issue #81 follow-up.
+  const freshArgs = ['--prefer-online', ...baseArgs];
   const noisyArgs = pnpm
-    ? ['--reporter=append-only', ...baseArgs]
-    : ['--loglevel=http', '--no-audit', '--no-fund', ...baseArgs];
+    ? ['--reporter=append-only', ...freshArgs]
+    : ['--loglevel=http', '--no-audit', '--no-fund', ...freshArgs];
   return runFile(log, bin, noisyArgs, { cwd: projectDir, env: installEnv() });
 }
 

package/server/steps/09-verify-deploy.mjs

@@ -130,11 +130,16 @@ async function verifyAppInSolution(log, pac, projectDir, solutionUniqueName, { p
     return membership;
   }
   if (membership.status === 'absent') {
-    const steps = SOLUTION_MEMBERSHIP.orphanRecoverySteps(solutionUniqueName, appDisplayName || 'this Code App');
-    for (const line of steps) log.fail(line);
-    // A confirmed orphan is a hard error in BOTH phases: pre-push (an UPDATE
-    // cannot fix it) and post-create (the create silently failed to associate).
-    throw new Error(`Code App is orphaned — NOT a component of solution "${solutionUniqueName}". ${phase === 'pre-push' ? 'A re-push will not fix this.' : 'The create did not associate it.'} See the recovery steps above.`);
+    // INFORMATIONAL ONLY — never block the deploy on this signal. The documented
+    // contract (learn.microsoft.com/power-apps/developer/code-apps/how-to/alm)
+    // is simply `pac code push --solutionName <name>`; association happens as
+    // part of that push. The export+type-300 component count below is a
+    // best-effort cross-check, NOT an authoritative source of truth — a clean
+    // export with zero Canvas App components does NOT reliably mean the app is
+    // orphaned. So we surface a hint and continue rather than throwing.
+    const hint = SOLUTION_MEMBERSHIP.orphanRecoverySteps(solutionUniqueName, appDisplayName || 'this Code App')[0];
+    log.warn(`${hint} If it is missing in the Maker Portal, add it with: Solutions → ${solutionUniqueName} → Add existing → App → Code app.`);
+    return membership;
   }
   log.warn(`Could not confirm solution membership for "${solutionUniqueName}" (${membership.detail}). Verify in the Maker Portal that the app is listed under it.`);
   return membership;