@jami-studio/core 0.92.12 → 0.92.14

package/corpus/core/CHANGELOG.md

@@ -1,5 +1,17 @@
 # @agent-native/core
 
+## 0.92.14
+
+### Patch Changes
+
+- Deploy builds sweep stale `.deploy-tmp` before running (both the per-app post-build entry and the workspace-deploy per-app clean list). A crashed prior build left partial artifacts that silently poisoned the next build for that app — observed as a cloudflare_pages unified build dying after the vite phases with no error output.
+
+## 0.92.13
+
+### Patch Changes
+
+- SSR heavy-lib stub: add `useMessagePartReasoning` to the named-export list. Core's chat message components import the hook from `@assistant-ui/react`; templates that list that package in `ssrStubs` (e.g. content) failed `agent-native build` with `[MISSING_EXPORT] "useMessagePartReasoning" is not exported by "\0agent-native-ssr-stub"`.
+
 ## 0.92.12
 
 ### Patch Changes

package/corpus/core/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@agent-native/core",
-  "version": "0.92.12",
+  "version": "0.92.14",
   "description": "Framework for agent-native application development — where AI agents and UI share SQL state, actions, and context",
   "homepage": "https://github.com/studio-jami/jami-studio#readme",
   "bugs": {

package/corpus/core/src/deploy/build.ts

@@ -3773,6 +3773,14 @@ export default bundle;
 async function main() {
   console.log(`[deploy] Building for ${preset}...`);
 
+  // Sweep stale .deploy-tmp before anything writes into it. A crashed prior
+  // build (any preset) leaves partial artifacts behind; both build paths
+  // mkdirSync over the dir without clearing it, and the stale contents can
+  // silently poison the next build (observed: an interrupted node-preset
+  // build made the following cloudflare_pages build fail with no error
+  // output). Fresh tmp every run is the invariant.
+  fs.rmSync(path.join(cwd, ".deploy-tmp"), { recursive: true, force: true });
+
   switch (preset) {
     case "cloudflare_pages":
     case "cloudflare-pages":