@indigoai-us/hq-cli 5.21.0 → 5.23.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.
Files changed (2) hide show
  1. package/CHANGELOG.md +38 -0
  2. package/package.json +2 -2
package/CHANGELOG.md CHANGED
@@ -2,6 +2,44 @@
2
2
 
3
3
  ## [Unreleased]
4
4
 
5
+ ## [5.22.0] — 2026-05-25
6
+
7
+ ### Changed
8
+
9
+ - Bumps `@indigoai-us/hq-cloud` to `~5.37.0` (was `~5.34.0`). Picks up
10
+ the 5.35 → 5.37 chain on top of yesterday's 5.34.0 cleanup.
11
+
12
+ - **5.35.0** — `.claude/state/` + `.claude/audit/` in
13
+ `DEFAULT_IGNORES`. Removes ~85% of the conflict-mirror class
14
+ observed during the 5.34.0 live cross-machine test. See
15
+ [hq-cloud#25](https://github.com/indigoai-us/hq-cloud/pull/25).
16
+ - **5.36.0** — two sync speedups: an lstat fast-path that skips
17
+ SHA-256 when `(size, mtimeMs)` match the journal baseline
18
+ (~5–10× on no-op syncs, which are most syncs), and a bounded-
19
+ parallel transfer pool (default 16, knob
20
+ `HQ_SYNC_TRANSFER_CONCURRENCY`) for uploads + downloads (4–8× on
21
+ transfer-heavy syncs). Codex P1 follow-ups serialize the
22
+ interactive conflict prompt under the pool and drain in-flight
23
+ transfers on worker error. See
24
+ [hq-cloud#26](https://github.com/indigoai-us/hq-cloud/pull/26).
25
+ - **5.37.0** — file mtime / birthtime preservation across sync.
26
+ Push stamps source-side `lstat.mtimeMs` (+ `birthtimeMs` when the
27
+ filesystem supports it AND differs from mtime) into S3 metadata as
28
+ `hq-mtime` / `hq-btime`. Pull applies the stamped value via
29
+ `utimesSync` after the byte write, falling back to write-time
30
+ when metadata is absent (back-compat). Symlinks skipped on both
31
+ sides. Composes cleanly with the 5.36.0 fast-path — the journal
32
+ records the post-utimes mtime, so the next sync correctly skips
33
+ re-hashing. Codex P2 widened the accepted mtime domain to include
34
+ `0` (Unix epoch, reproducible-builds clamp value) and negative
35
+ epochs (pre-1970). See
36
+ [hq-cloud#27](https://github.com/indigoai-us/hq-cloud/pull/27).
37
+
38
+ Live verified end-to-end on the macOS desktop ↔ Lightsail outpost
39
+ pair: bilateral convergence in 2–3 sync rounds, mtime round-trip
40
+ exact for 2020 / 2030 / epoch-0 / pre-epoch-negative test cases,
41
+ fast-path correctly skips post-utimes files on the next no-op.
42
+
5
43
  ## [5.21.0] — 2026-05-24
6
44
 
7
45
  ### Changed
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@indigoai-us/hq-cli",
3
- "version": "5.21.0",
3
+ "version": "5.23.0",
4
4
  "description": "HQ by Indigo management CLI — modules and cloud sync",
5
5
  "main": "dist/index.js",
6
6
  "bin": {
@@ -15,7 +15,7 @@
15
15
  "clean": "rm -rf dist"
16
16
  },
17
17
  "dependencies": {
18
- "@indigoai-us/hq-cloud": "~5.34.0",
18
+ "@indigoai-us/hq-cloud": "~5.38.0",
19
19
  "@indigoai-us/hq-onboarding": "^0.1.0",
20
20
  "@sentry/node": "^10.49.0",
21
21
  "chalk": "^5.3.0",