@neocompose/cli 0.70.1 → 0.70.2

package/CHANGELOG.md

@@ -1,5 +1,9 @@
 # Changelog
 
+## [0.70.2] - 2026-10-06
+
+- After `neo push` creates, replaces or moves a project file, its committed bytes become the file's merge base at its new path, as a pull's would. Before, the re-export after the push failed for every new file with "the pull recorded no bytes for it", and for a moved file with "missing". Either failure left the Unity project marked as a local export.
+
 ## [0.70.1] - 2026-10-06
 
 - `neo push` can upload a project file renamed with `@settings(name: ...)`. It used to stage the upload under the file's basename, so the commit failed with "Staged project file … did not match its source name".

package/dist/neo.mjs

@@ -31811,7 +31811,7 @@ var init_registry = __esm({
   "../packages/manifest/schema-contract/registry.mjs"() {
     "use strict";
     PROJECT_SCHEMA_CONTRACT = Object.freeze({
-      cliVersion: "0.70.1",
+      cliVersion: "0.70.2",
       projectFileUploadBatchSize: 32,
       documentRecords: {
         member: {
@@ -140070,8 +140070,8 @@ async function download(data, fileId, client, workspace) {
   }
   return { bytes: response.bytes, sha256: computed };
 }
-function committedProjectBinaryStateV4(previous, data) {
-  return isObjectRecord2(data) ? binaryState(previous.path, readSha256(data), data) : previous;
+function committedProjectBinaryStateV4(path, data) {
+  return binaryState(path, readSha256(data), isObjectRecord2(data) ? data : {});
 }
 function binaryState(path, sha2562, data) {
   return {
@@ -158782,6 +158782,18 @@ ${blockingErrors.map((error) => `  ${error.message}`).join("\n")}`
       data: local.fullData
     });
   }
+  for (const binary of localStatus.binaryFiles ?? []) {
+    const key = recordStateKey(
+      "project-file",
+      rewriteAssignedString(binary.fileId, replacements)
+    );
+    const record6 = nextRecords[key];
+    if (record6 === void 0 || !changedKeys.has(key)) continue;
+    nextRecords[key] = {
+      ...record6,
+      projectBinary: committedProjectBinaryStateV4(binary.path, record6.data)
+    };
+  }
   const previousState = workspace.state;
   workspace.state = {
     ...previousState,
@@ -159014,14 +159026,13 @@ function foldChangedRecords(previous, changedRecords) {
         `Changed record "${key}" response is missing its snapshot content hash.`
       );
     }
-    const projectBinary = records2[key]?.projectBinary;
     records2[key] = {
       recordKind,
       recordId,
       contentHash: snapshot.contentHash,
       data: changed.data,
       file: records2[key]?.file,
-      projectBinary: projectBinary && committedProjectBinaryStateV4(projectBinary, changed.data)
+      projectBinary: records2[key]?.projectBinary
     };
   }
   return records2;
@@ -181274,7 +181285,7 @@ There is no --keep-current: preserving current semantic state defines flatten.
 async function main() {
   const args = parseArgs(process.argv.slice(2));
   if (args.command === "--version") {
-    console.log("0.70.1");
+    console.log("0.70.2");
     return;
   }
   if (args.command === null || args.command === "help" || args.command === "--help" || args.command === "-h") {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@neocompose/cli",
-  "version": "0.70.1",
+  "version": "0.70.2",
   "description": "Neo Compose native project-source CLI with bidirectional sync.",
   "license": "MIT",
   "type": "module",

package/skills/neocompose-cli/SKILL.md

@@ -9,7 +9,7 @@ description: >-
   `@neocompose/cli` or `node cli/bin/neo.mjs` in the neo-compose repository.
 ---
 
-<!-- reviewed-through-cli: 0.70.1 -->
+<!-- reviewed-through-cli: 0.70.2 -->
 
 # Neo Compose CLI
 

package/skills/neocompose-cli/references/cli-development.md

@@ -110,7 +110,7 @@ wrappers.
 The marker near the top of `SKILL.md` must exactly match the package version:
 
 ```html
-<!-- reviewed-through-cli: 0.70.1 -->
+<!-- reviewed-through-cli: 0.70.2 -->
 ```
 
 The quoted version above is checked too, so this instruction cannot go stale