claude-nomad 0.62.5 → 0.63.0

package/CHANGELOG.md

@@ -1,5 +1,53 @@
 # Changelog
 
+## [0.63.0](https://github.com/funkadelic/claude-nomad/compare/v0.62.6...v0.63.0) (2026-07-31)
+
+### What's new
+
+- **Windows: your own edits to shared config are no longer reverted.** On Windows, editing a synced
+  file like `~/.claude/CLAUDE.md` and then running `nomad pull` overwrote it from the repo, and
+  `nomad sync` went on to publish the reverted version, silently undoing the change you ran sync to
+  publish. Your edit is now carried into the sync repo first, so it survives the pull and gets
+  published instead.
+- **The secret prompt on push is readable and asks once per secret.** When a push finds a possible
+  secret it used to ask the same question several times over for one secret, and the snippet it
+  showed was mostly noise. It now asks once per secret and describes what was actually found, so you
+  can tell a real credential from a false positive at a glance.
+- **Three ways that prompt could show you a secret it meant to hide are closed**, along with a case
+  where allowing one false positive could quietly let a real secret through beside it on the same
+  line.
+
+
+### Added
+
+* **pull:** stop Windows pulls reverting unpublished shared-config edits ([#476](https://github.com/funkadelic/claude-nomad/issues/476)) ([16fa692](https://github.com/funkadelic/claude-nomad/commit/16fa6925477fb56dd0104c8106cbdaf2ff27539d))
+
+
+### Fixed
+
+* **push:** rework the leak recovery prompt and close disclosure paths ([#477](https://github.com/funkadelic/claude-nomad/issues/477)) ([a1ccb9a](https://github.com/funkadelic/claude-nomad/commit/a1ccb9af7ac718ee43a5629f9d5ee6ca89c84114))
+
+
+### Testing
+
+* **push:** close doMock/doUnmock asymmetry in the push cluster ([#475](https://github.com/funkadelic/claude-nomad/issues/475)) ([9c0d5ab](https://github.com/funkadelic/claude-nomad/commit/9c0d5abf32e3478b85550ee18365bffab425f193))
+
+
+### Dependencies
+
+* bump actions/checkout from 7.0.0 to 7.0.1 ([#470](https://github.com/funkadelic/claude-nomad/issues/470)) ([4b74689](https://github.com/funkadelic/claude-nomad/commit/4b74689b6b857aeddeb040113e50488fdc0ab2fa))
+* bump actions/labeler from 6.2.0 to 7.0.0 ([#469](https://github.com/funkadelic/claude-nomad/issues/469)) ([8a6d413](https://github.com/funkadelic/claude-nomad/commit/8a6d413aa815fa7c2070c29c76d5d5688146ffbd))
+* bump the codeql-action group with 2 updates ([#468](https://github.com/funkadelic/claude-nomad/issues/468)) ([d19e7fd](https://github.com/funkadelic/claude-nomad/commit/d19e7fdad1d24f8917c10c9e398cc8c89db9c289))
+* bump the dev-dependencies group across 1 directory with 6 updates ([#471](https://github.com/funkadelic/claude-nomad/issues/471)) ([971a82f](https://github.com/funkadelic/claude-nomad/commit/971a82f6dac29dacfa0681b15b33e616dbbdef99))
+* bump the prod-dependencies group across 1 directory with 2 updates ([#474](https://github.com/funkadelic/claude-nomad/issues/474)) ([ea259dd](https://github.com/funkadelic/claude-nomad/commit/ea259dd169ce2d7beba9bef83581199ebea5a167))
+
+## [0.62.6](https://github.com/funkadelic/claude-nomad/compare/v0.62.5...v0.62.6) (2026-07-25)
+
+
+### Fixed
+
+* **nomad:** treat a Ctrl+C prompt abort as a user cancel ([#466](https://github.com/funkadelic/claude-nomad/issues/466)) ([6250627](https://github.com/funkadelic/claude-nomad/commit/62506279155fe02c067675271fa9bc02f341a14b))
+
 ## [0.62.5](https://github.com/funkadelic/claude-nomad/compare/v0.62.4...v0.62.5) (2026-07-24)
 
 

package/README.md

@@ -119,8 +119,22 @@ $ nomad pull
 
 ### Windows
 
-claude-nomad also runs natively on Windows, no WSL required (WSL2 still works fine too, if you
-prefer it). The steps are the same as above with a couple of PowerShell-specific swaps:
+claude-nomad runs natively on Windows (PowerShell or cmd), and WSL2 works too. The everyday loop is
+the same either way; the difference is under the hood.
+
+On macOS, Linux, and WSL2, claude-nomad symlinks your shared config into `~/.claude/`, so there is
+only ever one file: the one in your sync repo. Native Windows cannot use symlinks, because creating
+one there needs Developer Mode or admin rights, so claude-nomad keeps a real copy there instead.
+That leaves two files to keep in step, and claude-nomad does it for you: `nomad pull` and
+`nomad sync` both copy your edits into the repo before they fetch, so an unpublished edit is never
+overwritten. Enabling Developer Mode does not change this; copies are used on every native Windows
+host either way.
+
+Two things are genuinely Windows-only, both covered in the bullets below: a `.gitleaksignore` allow
+entry may not travel to a macOS or Linux host, and deep session paths can hit Windows's
+260-character path limit.
+
+The native Windows steps are the same as above with a couple of PowerShell-specific swaps:
 
 ```powershell
 # 1. Install the CLI.
@@ -148,13 +162,14 @@ A few Windows-specific things worth knowing:
   use Scoop). `nomad doctor` prints the same hint whenever gitleaks is missing from PATH.
 - **Shared config is copied, not symlinked.** On macOS and Linux, files like `CLAUDE.md` and your
   skills live in the sync repo and are symlinked into `~/.claude/`, so there is one source of truth
-  on disk. Creating a symlink on Windows needs Developer Mode or admin rights, so on Windows these
-  are real copies instead. What this means for you: after editing a shared file on Windows, run
-  `nomad push` before your next `nomad pull` or `nomad sync`. `nomad sync` always pulls first, and
-  the pull half overlays the repo's copy onto yours (the prior content is snapshotted to the backup
-  dir first, so it is recoverable, but it is still reverted in place); pushing first is what
-  actually captures your edit. This is the same behavior claude-nomad's `skills/` sync already has
-  on every platform.
+  on disk. Creating a symlink on Windows needs Developer Mode or admin rights, so on native Windows
+  these are real copies instead, whether or not you have Developer Mode enabled. WSL2 is unaffected
+  and behaves like Linux. What this means for you: nothing extra. On Windows both `nomad pull` and
+  `nomad sync` mirror your local copies into the repo before they fetch, so an unpublished edit is
+  captured rather than reverted. The one command that deliberately takes the repo's version is
+  `nomad pull --force-remote`, which is what that flag is for; the copy it replaces is snapshotted
+  to the backup dir first. This is the same behavior claude-nomad's `skills/` sync already has on
+  every platform.
 - **A `.gitleaksignore` allow entry may not travel across hosts.** gitleaks fingerprints each
   finding using the file path exactly as it saw it: backslashes on Windows, forward slashes on
   macOS/Linux. If you allow a finding with `nomad push --allow` (or `nomad allow`) on Windows, the
@@ -313,6 +328,7 @@ branch on `$?` without parsing stderr text.
 | 2    | Usage           | Bad argv: an unknown subcommand, an unknown flag, or a malformed flag value.         |
 | 4    | Conflict        | The sync repo is wedged (e.g. an unresolved rebase) and needs manual git resolution. |
 | 5    | Leak blocked    | gitleaks confirmed a secret in the staged tree and the push was aborted.             |
+| 130  | Interrupted     | You pressed Ctrl+C at an interactive prompt, so nomad stopped without finishing.     |
 
 A run skipped because another nomad process already holds the lock also exits 0: this is an
 intentional no-op skip, not a failure, so a backgrounded shell-rc or cron invocation never raises a
@@ -323,7 +339,8 @@ false alarm from a concurrent run. Value `3` is reserved for future use.
 If `nomad` ever hits an unexpected bug, it no longer dumps a raw stack trace at you. Instead it
 prints a short "this looks like a bug" banner (with a link to the issue tracker) and writes a small
 report you can attach to a bug report if you choose. The exit code is unchanged: an unexpected crash
-exits `1`, and a documented failure still exits with its own code from the table above.
+exits `1`, and a documented failure still exits with its own code from the table above. A prompt you
+cancel yourself is not a crash: it exits `130` and writes no report.
 
 What this means for you: