@williamthorsen/nmr 0.43.0 → 0.45.0

package/.meta/changelog.json

@@ -1,4 +1,172 @@
 [
+  {
+    "version": "0.45.0",
+    "date": "2026-10-12",
+    "sections": [
+      {
+        "title": "🎉 Features",
+        "audience": "all",
+        "items": [
+          {
+            "description": "Adds `maintenance.auto=false` to the git config that the Vitest git-isolation setup file injects, so that a git command run by a test does not start a detached `git maintenance` process that can still be writing under `.git` when the test removes the repository. (#1033)",
+            "hash": "a46223192e0dac47366d7c9c46acb3a1234d1dfc",
+            "entry": 1
+          }
+        ]
+      },
+      {
+        "title": "🐛 Bug fixes",
+        "audience": "all",
+        "items": [
+          {
+            "description": "Fixes the issue that `nmr-fmt` failed a run in which every path matched by the pathspecs was one that it skips, such as a symlink, a submodule gitlink, or an unreadable file, and makes such a run exit 0 and name the skipped paths on stderr. (#1010)",
+            "hash": "aef8382212b6ab4b5e48fd2086e018a6e9da2cef",
+            "entry": 1
+          },
+          {
+            "description": "Fixes the issue that a `rootScripts` or `workspaceScripts` entry in `.config/nmr.config.ts` that names its own key, as a shell segment or as a step-list element, re-entered nmr without bound, by rejecting the entry when the config loads with an error that names the file, the field, the key, and the edit that resolves it. (#1011)",
+            "hash": "6c61d03429b378a131910c3980b77caf29fd0e51",
+            "entry": 1
+          },
+          {
+            "description": "Fixes the issue that a package's own `package.json` entry running `nmr -R <same command>` re-entered that package without bound instead of being discarded or rejected as a self-reference. (#1011)",
+            "hash": "6c61d03429b378a131910c3980b77caf29fd0e51",
+            "entry": 2
+          },
+          {
+            "description": "Fixes the issue that nmr treated a root entry such as `pnpm --recursive exec nmr build` as a re-invocation of its own command, because it ignored the `-r`, `--filter`, and `-w` flags that pnpm applies to the nmr that it launches. (#1011)",
+            "hash": "6c61d03429b378a131910c3980b77caf29fd0e51",
+            "entry": 3
+          },
+          {
+            "description": "Fixes the issue that `nmr` hung when a script entry re-entered its own command in the same directory without nmr recognizing the self-reference, as `nmr -F own-pkg build` in `own-pkg`'s own `build` or a cycle through two entries does, by failing the run with an error that names the command and the directory and lists the commands that the run had entered, outermost first. (#1012)",
+            "hash": "db41c4b556572ede212a409fce8d845af3572f19",
+            "entry": 1
+          },
+          {
+            "description": "Fixes the issue that the test-tier definitions in `vitest.md` gave a test that starts its own loopback server three defensible tiers: `tool` is now a process that the test starts or a program that the environment supplies, `localhost` a service already running on this machine, and an in-process server from the package's own dependency closure `unit`. (#1023)",
+            "hash": "77709de748dc7d06e76dea179f8b8741d3b8a38a",
+            "entry": 1
+          },
+          {
+            "description": "Fixes the issue that `nmr`'s warning about a `package.json` script that runs `nmr` through a shell sent an entry whose whole value is `nmr <name>` to `.config/nmr.config.ts`, when the accurate edit is to replace that value with the command of the `<name>` script in the same file. (#1030)",
+            "hash": "ff02b6eb099cbfd92616946afdabac737c955c1c",
+            "entry": 1
+          }
+        ]
+      },
+      {
+        "title": "♻️ Refactoring",
+        "audience": "dev",
+        "items": [
+          {
+            "description": "Moves the work of `runInvocation` in `nmr` into the phase functions `establishInvocation`, `planRun`, and `executePlan`, which `runCli` calls in order, and changes `runGated` and `reportRecording` to take a named `RunPlan` in place of an options object that repeated its fields. (#1014)",
+            "hash": "c761afb7f37e64ce89b83178cfcc4bc4933a8587",
+            "entry": 1
+          }
+        ]
+      },
+      {
+        "title": "🧪 Tests",
+        "audience": "dev",
+        "items": [
+          {
+            "description": "Replaces the `GIT_CEILING_DIRECTORIES` stub with a `GIT_DIR` stub that points to a missing path in the no-repository test of `check-cache-gate.tool.test.ts`, and sets `maintenance.auto` to `false` in the file's fixture repository, so that git neither finds a leftover of the removed `repo/.git` nor starts a detached maintenance process that writes under `.git`. (#1032)",
+            "hash": "66996a15b7ef27374c81212f10a20efd3d48f4ff",
+            "entry": 1
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "version": "0.44.0",
+    "date": "2026-10-11",
+    "sections": [
+      {
+        "title": "🎉 Features",
+        "audience": "all",
+        "items": [
+          {
+            "description": "Enables Prettier's content-keyed cache in `nmr-fmt` (run by `nmr fmt` and `nmr fmt:check`), which skips each file whose content, Prettier version, resolved options, and lockfile are unchanged since a run that passed it, and adds `--no-cache` and `NMR_NO_CACHE=1` to bypass it. (#993)",
+            "hash": "8c49c92f557273f018a1e12709146e713d49d223",
+            "entry": 1
+          },
+          {
+            "description": "Adds the `shouldRunInBackground` field to a composite element in `.config/nmr.config.ts`, which starts the step, runs the steps after it without waiting, prints the step's output whole after the step ends, and fails the composite if the step fails. (#1003)",
+            "hash": "683232387f38e81916f20718e0d4e9a7abb3d3ef",
+            "entry": 1
+          },
+          {
+            "description": "Adds a `self-hosted runner` checklist to nmr's readyup kit, which reads the repo's GitHub settings through `gh`, recommends setting `CI_RUNS_ON` when a private repo with an online self-hosted runner and compatible workflows has not set it, and warns about each failing condition once the variable is set. (#1006)",
+            "hash": "e7ee5fe2e147d737d11a302403b4b342d64de194",
+            "entry": 1
+          },
+          {
+            "description": "Adds the root-only config key `selfHostedRunner.exempt`, a non-empty reason that stops the kit from recommending `CI_RUNS_ON` for a repo that qualifies for the self-hosted runners but stays off them. (#1006)",
+            "hash": "e7ee5fe2e147d737d11a302403b4b342d64de194",
+            "entry": 2
+          }
+        ]
+      },
+      {
+        "title": "🪦 Removed",
+        "audience": "all",
+        "items": [
+          {
+            "description": "Removes the zero-argument form of `getDefaultRootScripts` from the `@williamthorsen/nmr/scripts` export, which now requires the monorepo root so that it can read the declared workspaces. (#992)",
+            "breaking": true,
+            "migration": "Pass the monorepo root to `getDefaultRootScripts`, as in `getDefaultRootScripts(monorepoRoot)`; a directory without a `pnpm-workspace.yaml` returns root lint commands that do not exclude any directory, where the old call excluded `packages/**`.",
+            "hash": "075a76eaecb7304f6645c917693c785c1e08b20b",
+            "entry": 2
+          }
+        ]
+      },
+      {
+        "title": "🐛 Bug fixes",
+        "audience": "all",
+        "items": [
+          {
+            "description": "Fixes the issue that `root:lint`, `root:lint:check`, and `root:lint:strict` linted every workspace outside `packages/` under the root ESLint config, by excluding each workspace package that `pnpm-workspace.yaml` declares, with its `!` exclusions honored, in place of the fixed `packages/**`. (#992)",
+            "hash": "075a76eaecb7304f6645c917693c785c1e08b20b",
+            "entry": 1
+          },
+          {
+            "description": "Fixes the issue that `defineConfig({ mode: undefined })` emptied the `nmr upgrade` report, by translating a cleared `mode` into the `'default'` mode of taze (the upgrade tool that `nmr upgrade` runs), which follows the range that each dependency declares. (#1008)",
+            "hash": "5813dcbe9d11fce34edaf819a264eb634f948d3c",
+            "entry": 1
+          }
+        ]
+      },
+      {
+        "title": "⚡ Performance",
+        "audience": "all",
+        "items": [
+          {
+            "description": "Sets `maxWorkers: 3` on every project built by `defineVitestConfig` and `defineRootVitestConfig` when the machine has 2 or fewer cores, such as GitHub's standard runner for a private repo, on which Vitest's default ran every test file serially on one worker. (#994)",
+            "hash": "9a4494c2ff740c2b278a2e28bb05a4ab117134ba",
+            "entry": 1
+          },
+          {
+            "description": "Changes the default `check` and `check:strict` to start lint first and run it in the background, so that a local check, `nmr ci`, and `nmr prepush` no longer wait for type-aware lint to finish before typecheck, the format check, and the tests run. (#1003)",
+            "hash": "683232387f38e81916f20718e0d4e9a7abb3d3ef",
+            "entry": 2
+          }
+        ]
+      },
+      {
+        "title": "📚 Documentation",
+        "audience": "dev",
+        "items": [
+          {
+            "description": "Documents in `docs/vitest.md` that Vitest's `--maxWorkers` flag has no effect on a machine with 2 or fewer cores, and that `VITEST_MAX_WORKERS`, `--no-file-parallelism`, or `maxWorkers` in the `project` seam overrides the default there. (#994)",
+            "hash": "9a4494c2ff740c2b278a2e28bb05a4ab117134ba",
+            "entry": 2
+          }
+        ]
+      }
+    ]
+  },
   {
     "version": "0.43.0",
     "date": "2026-10-09",