@nemus-cli/nemus 0.2.2 → 0.2.4

package/CHANGELOG.md

@@ -7,6 +7,34 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.2.4] - 2026-08-25
+
+### Changed
+
+- Dependencies: `commander` 14 → 15 (runtime); dev tooling `@types/node` 22 → 26
+  and `vitest` 3 → 4.
+- CI: pinned `actions/checkout` → v7, `actions/setup-node` → v7, and
+  `actions/github-script` → v9, which clears the "Node.js 20 is deprecated"
+  warnings on every run.
+
+### Deferred
+
+- `react` 18 → 19 is held: `ink` 5's bundled `react-reconciler` targets React 18
+  internals, so React 19 needs the `ink` 7 major (a TUI-tested change).
+- `inquirer` 8 → 14 and `inquirer-autocomplete-prompt` 2 → 3 are held: inquirer
+  v9+ split into `@inquirer/prompts`, so this is a code migration, not a bump.
+- `typescript` 7 is held: it removes `moduleResolution: node10`, requiring a
+  `tsconfig` migration.
+
+## [0.2.3] - 2026-08-25
+
+### Fixed
+
+- The one-time `~/.workspace-manager-cache` → `~/.nemus` migration no longer
+  copies `last-version-check.json`. If the old (shared) path held another tool's
+  update-check cache, inheriting it could make nemus report a wrong "latest"
+  version until the entry expired; skipping it forces one fresh lookup instead.
+
 ## [0.2.2] - 2026-08-25
 
 ### Changed
@@ -97,7 +125,9 @@ Initial open-source release of **Nemus**.
 - Automatic retries with backoff on flaky network operations.
 - Optional shell integration (auto-cd on create + quick-navigate helper).
 
-[Unreleased]: https://github.com/me-public/nemus/compare/v0.2.2...HEAD
+[Unreleased]: https://github.com/me-public/nemus/compare/v0.2.4...HEAD
+[0.2.4]: https://github.com/me-public/nemus/compare/v0.2.3...v0.2.4
+[0.2.3]: https://github.com/me-public/nemus/compare/v0.2.2...v0.2.3
 [0.2.2]: https://github.com/me-public/nemus/compare/v0.2.1...v0.2.2
 [0.2.1]: https://github.com/me-public/nemus/compare/v0.2.0...v0.2.1
 [0.2.0]: https://github.com/me-public/nemus/compare/v0.1.0...v0.2.0

package/dist/utils/config.js

@@ -53,11 +53,20 @@ const LEGACY_CACHE_DIR = path.join(HOME_DIR, '.workspace-manager-cache');
  * location (no env override) and the new dir doesn't exist yet. Copies rather
  * than moves, so any other tool that happened to share the old path is left
  * untouched; a failure is harmless because a fresh dir is created on first write.
+ *
+ * `last-version-check.json` is deliberately NOT migrated: the old path could be
+ * shared by another tool whose "latest version" is unrelated to nemus, and
+ * copying it would make the update check report a wrong version until the entry
+ * expires. Skipping it just forces one fresh lookup.
  */
+const MIGRATION_SKIP = new Set(['last-version-check.json']);
 function migrateLegacyCacheDir(targetDir) {
     try {
         if (targetDir === DEFAULT_CACHE_DIR && !fs.existsSync(targetDir) && fs.existsSync(LEGACY_CACHE_DIR)) {
-            fs.cpSync(LEGACY_CACHE_DIR, targetDir, { recursive: true });
+            fs.cpSync(LEGACY_CACHE_DIR, targetDir, {
+                recursive: true,
+                filter: (src) => !MIGRATION_SKIP.has(path.basename(src)),
+            });
         }
     }
     catch {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@nemus-cli/nemus",
-  "version": "0.2.2",
+  "version": "0.2.4",
   "description": "Nemus — a CLI for managing multi-repository workspaces. Create, sync, and operate across dozens of repos with a single command, and wire them up to your favorite coding agent.",
   "keywords": [
     "workspace",
@@ -66,7 +66,7 @@
   "dependencies": {
     "@modelcontextprotocol/sdk": "^1.26.0",
     "cli-progress": "^3.12.0",
-    "commander": "^14.0.3",
+    "commander": "^15.0.0",
     "fuzzy": "^0.1.3",
     "ink": "^5.0.0",
     "ink-select-input": "^6.0.0",
@@ -74,17 +74,17 @@
     "inquirer": "^8.0.0",
     "inquirer-autocomplete-prompt": "^2.0.0",
     "markdown-table": "^3.0.3",
-    "react": "^18.2.0",
+    "react": "^18.3.1",
     "zod": "^4.3.6"
   },
   "devDependencies": {
     "@types/cli-progress": "^3.11.0",
     "@types/inquirer": "^9.0.3",
     "@types/inquirer-autocomplete-prompt": "^2.0.0",
-    "@types/node": "^22.14.0",
-    "@types/react": "^18.2.0",
+    "@types/node": "^26.3.0",
+    "@types/react": "^18.3.31",
     "ts-node": "^10.9.1",
     "typescript": "^5.9.3",
-    "vitest": "^3.0.0"
+    "vitest": "^4.1.11"
   }
 }

package/src/utils/config.test.ts

@@ -236,6 +236,19 @@ describe('config', () => {
       expect(fs.existsSync(path.join(tempDir, '.workspace-manager-cache', 'suites.json'))).toBe(true);
     });
 
+    it('does not migrate last-version-check.json (avoids inheriting a foreign latest)', async () => {
+      delete process.env.NEMUS_CACHE_DIR;
+      delete process.env.WORKSPACE_MANAGER_CACHE_DIR;
+      const legacy = path.join(tempDir, '.workspace-manager-cache');
+      fs.writeFileSync(path.join(legacy, 'suites.json'), '{"x":1}');
+      fs.writeFileSync(path.join(legacy, 'last-version-check.json'), '{"latestVersion":"99.0.0"}');
+      vi.resetModules();
+      await loadModule();
+      // other state migrates, but the version-check cache is left behind
+      expect(fs.existsSync(path.join(tempDir, '.nemus', 'suites.json'))).toBe(true);
+      expect(fs.existsSync(path.join(tempDir, '.nemus', 'last-version-check.json'))).toBe(false);
+    });
+
     it('does not migrate when the new dir already exists', async () => {
       delete process.env.NEMUS_CACHE_DIR;
       delete process.env.WORKSPACE_MANAGER_CACHE_DIR;

package/src/utils/config.ts

@@ -16,11 +16,20 @@ const LEGACY_CACHE_DIR = path.join(HOME_DIR, '.workspace-manager-cache');
  * location (no env override) and the new dir doesn't exist yet. Copies rather
  * than moves, so any other tool that happened to share the old path is left
  * untouched; a failure is harmless because a fresh dir is created on first write.
+ *
+ * `last-version-check.json` is deliberately NOT migrated: the old path could be
+ * shared by another tool whose "latest version" is unrelated to nemus, and
+ * copying it would make the update check report a wrong version until the entry
+ * expires. Skipping it just forces one fresh lookup.
  */
+const MIGRATION_SKIP = new Set(['last-version-check.json']);
 function migrateLegacyCacheDir(targetDir: string): void {
   try {
     if (targetDir === DEFAULT_CACHE_DIR && !fs.existsSync(targetDir) && fs.existsSync(LEGACY_CACHE_DIR)) {
-      fs.cpSync(LEGACY_CACHE_DIR, targetDir, { recursive: true });
+      fs.cpSync(LEGACY_CACHE_DIR, targetDir, {
+        recursive: true,
+        filter: (src) => !MIGRATION_SKIP.has(path.basename(src)),
+      });
     }
   } catch {
     // best-effort — ignore and let the dir be created lazily