taodengandClaude Opus 4.7 45d067bdaa fix(doctor): dynamic latest_version from origin/main; release v3.15.1 ...

v3.15.0 doctor used a hard-coded `latest = "v3.14.0"` fallback, causing
any v3.15.0+ install to report kind=upgrade against a stale value.
`ocp update` would then attempt `git checkout v3.14.0` — a downgrade.

Doctor now fetches `git -C ~/ocp show origin/main:package.json` to
determine the actual latest. On failure (offline, fresh clone, no
remote), falls back to currentVersion so kind=noop instead of
recommending a downgrade.

Regression test added: doctor with unreachable ocpDir falls back to
currentVersion as latest (not the old hardcoded v3.14.0).

Caught during v3.15.0 post-deploy verification on home-mac: ./ocp
doctor reported `kind=upgrade` immediately after v3.15.0 install,
which would have been a critical user-facing bug.

No cli.js citation needed: this is OCP-internal doctor logic with
no corresponding cli.js operation.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

2026-05-11 07:00:00 +10:00

..

lib

feat(upgrade): ocp doctor + cross-version ocp update + rollback + AI prompts (#91)

2026-05-11 06:56:17 +10:00

doctor.mjs

fix(doctor): dynamic latest_version from origin/main; release v3.15.1

2026-05-11 07:00:00 +10:00

heartbeat-field-check.sh

chore(repo): add .gitignore for runtime artifacts; commit scripts/heartbeat-field-check.sh (#55)

2026-05-05 09:43:47 +10:00

sync-openclaw.mjs

feat(sync): idempotent OpenClaw registry sync in ocp update (#31)

2026-04-20 17:35:41 +10:00

upgrade.mjs

feat(upgrade): ocp doctor + cross-version ocp update + rollback + AI prompts (#91)

2026-05-11 06:56:17 +10:00