@solidactions/cli 3.24.0 → 3.25.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -523,6 +523,8 @@ solidactions doc upload logo-v2.png --replace marketing/logo.png
523
523
 
524
524
  **`doc pull` never writes through a link or over bytes it does not own.** It refuses before writing anything when a target is a symbolic link, sits under a linked folder inside the destination, or resolves outside it, with or without `--overwrite`. A local file the destination does not track (or tracks without a recorded hash) is replaced only with `--overwrite`; `-y` only answers the confirmation. A file that already holds exactly the server's bytes is simply adopted. A media doc whose download fails is not tracked over a local file.
525
525
 
526
+ **`doc pull` stops on the first error and records exactly what it wrote.** `doc pull` writes each file through a temp file beside it and renames it into place, in order, and saves the manifest last. If a write fails, or a file you changed in the meantime (or a folder where a doc goes) is in the way, the pull stops there with one line saying how many files were updated: the files before it stay written and are recorded in the manifest with their own checksums, the rest keep their bytes and their earlier entries, and nothing is rolled back or deleted. Pull again and it completes the job; a file that already holds exactly the bytes the pull would write is never treated as a local change. While it runs, a pull keeps one lock file, `.solidactions-docs.json.lock`, in the destination: a second pull into the same destination (or two started together) refuses and changes nothing, so two pulls never write into one folder; run it again when the first has finished. The pull removes its lock when it ends, including on an error or an interrupt. If the process is killed (SIGKILL) while writing, the manifest is the old one, the lock file is left behind, and tracked files are always re-checked by hash, so nothing is overwritten silently: if the line says another pull may be writing but none is running, delete that lock file and pull again. A doc or folder whose name would be `.solidactions-docs.json`, `.solidactions-docs.json.lock` or start with `.sa-write-` is written under a name with a leading `_`, and names that differ only by case or Unicode normalisation always get distinct names. There is no guarantee after a power loss.
527
+
526
528
  You do **not** need `--overwrite` to keep an edited file whose doc was deleted on the server — that case is handled by deletion propagation above, on the default path, and the file is kept with a warning.
527
529
 
528
530
  **Getting a doc id.** `doc upload --replace` accepts a docs path (`marketing/hero.png`), so you rarely need an id. If you want one, `doc pull` records it per file in the destination's `.solidactions-docs.json` sidecar, and `import_outputs` returns the ids it created. Note that `--replace` does not update a pulled directory's manifest. If you replace a tracked image out-of-band and leave the local file untouched, the next `doc push` reports it as **unchanged** and does nothing — the content hash matches, so `push` never asks the server. (Edit the local file too, and the drift guard fires as expected.) Re-pull to resync the manifest.
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "schema_version": 1,
3
3
  "cli_name": "solidactions",
4
- "cli_version": "3.24.0",
4
+ "cli_version": "3.25.0",
5
5
  "global_options": [
6
6
  {
7
7
  "flags": "-V, --version",