breakage 0.8.2 → 0.8.4

package/README.md

@@ -4,14 +4,6 @@ Run yesterday’s tests against tomorrow’s release.
 
 Command line tooling to detect breaking changes before you ship them.
 
-## migrating from break-check
-
-Breakage continues [break-check](https://github.com/jeremybanka/wayforge/tree/break-check%400.8.1/packages/break-check) in its own repository. Install `breakage`, replace the `break-check` command with `breakage`, and rename `break-check.config.json` to `breakage.config.json`. Configuration keys and check outcomes are unchanged. Regenerate schemas with `breakage schema`; generated files now use the `breakage` prefix. Reinstall shell completions with `breakage completion install <shell>`.
-
-For programmatic use, import `breakage`, `BreakageOptions`, and `BreakageOutcome` from `breakage` in place of `breakCheck`, `BreakCheckOptions`, and `BreakCheckOutcome` from `break-check`.
-
-Finish active break-check runs and recover any interrupted runs before switching. Breakage stores new recovery records under `breakage/` in the worktree's Git directory and its fetch lock at `breakage-fetch.lock` in the common Git directory.
-
 ## can i use breakage?
 
 breakage is a tool for projects where
@@ -90,8 +82,8 @@ Add these scripts to the tested package, preserving your existing runner and cer
 ```json
 {
 	"scripts": {
-		"test:breaks:prelude": "breakage prelude --out .breakage/baseline.json",
-		"test:breaks": "breakage --baseline-file .breakage/baseline.json"
+		"test:breakage:prelude": "breakage prelude --out .breakage/baseline.json",
+		"test:breakage": "breakage --baseline-file .breakage/baseline.json"
 	}
 }
 ```
@@ -101,11 +93,11 @@ Use [Turbo's deferred hashing](https://turborepo.dev/docs/reference/configuratio
 ```json
 {
 	"tasks": {
-		"test:breaks:prelude": {
+		"test:breakage:prelude": {
 			"cache": false
 		},
-		"test:breaks": {
-			"dependsOn": ["test:breaks:prelude", "^build"],
+		"test:breakage": {
+			"dependsOn": ["test:breakage:prelude", "^build"],
 			"inputs": [
 				"$TURBO_DEFAULT$",
 				{ "mode": "jit", "globs": [".breakage/baseline.json"] }
@@ -116,7 +108,7 @@ Use [Turbo's deferred hashing](https://turborepo.dev/docs/reference/configuratio
 }
 ```
 
-Run `turbo run test:breaks` as usual. The prelude runs even when the compatibility check hits its cache; a failed prelude prevents the downstream task from replaying a cached success. Keep all additional runner, helper, configuration, environment, and certification inputs in the compatibility task's hash, including release-plan files outside the package directory. Keep upstream `^build` prerequisites; the tested package does not need a self-build preflight. For runners without deferred hashing, finish the prelude before starting the task runner and include its snapshot in the check's cache key.
+Run `turbo run test:breakage` as usual. The prelude runs even when the compatibility check hits its cache; a failed prelude prevents the downstream task from replaying a cached success. Keep all additional runner, helper, configuration, environment, and certification inputs in the compatibility task's hash, including release-plan files outside the package directory. Keep upstream `^build` prerequisites; the tested package does not need a self-build preflight. For runners without deferred hashing, finish the prelude before starting the task runner and include its snapshot in the check's cache key.
 
 The JavaScript API exports `breakagePrelude({ out, tagPattern, baseDirname })` and accepts `baselineFile` in `breakage` options. Without `baselineFile`, the existing single-command discovery behavior is preserved.
 
@@ -253,3 +245,11 @@ These aliases work alongside the original option names. Configuration file keys
 | `--outdir` (schema command) | `--out-dir`                    |
 
 After successful parsing, breakage warns on stderr about unknown options and options that do not apply to the selected command. Warnings appear before check output is captured and do not change the command's exit status.
+
+## migrating from break-check
+
+Breakage continues [break-check](https://github.com/jeremybanka/wayforge/tree/break-check%400.8.1/packages/break-check) in its own repository. Install `breakage`, replace the `break-check` command with `breakage`, and rename `break-check.config.json` to `breakage.config.json`. Configuration keys and check outcomes are unchanged. Regenerate schemas with `breakage schema`; generated files now use the `breakage` prefix. Reinstall shell completions with `breakage completion install <shell>`.
+
+For programmatic use, import `breakage`, `BreakageOptions`, and `BreakageOutcome` from `breakage` in place of `breakCheck`, `BreakCheckOptions`, and `BreakCheckOutcome` from `break-check`.
+
+Finish active break-check runs and recover any interrupted runs before switching. Breakage stores new recovery records under `breakage/` in the worktree's Git directory and its fetch lock at `breakage-fetch.lock` in the common Git directory.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "breakage",
-  "version": "0.8.2",
+  "version": "0.8.4",
   "description": "Run yesterday’s tests against tomorrow’s release.",
   "homepage": "https://github.com/jeremybanka/breakage#readme",
   "bugs": "https://github.com/jeremybanka/breakage/issues",
@@ -45,7 +45,8 @@
     "postversion": "dprint fmt package.json",
     "schema": "bun src/breakage.x.ts --outdir=dist -- schema",
     "pretest": "pnpm run build",
-    "test": "bun test -- ./__tests__",
-    "test:watch": "bun test --watch -- ./__tests__"
+    "test": "BREAKAGE_CLI_ENTRYPOINT=./src/breakage.x.ts bun test -- ./__tests__ ./tests/public",
+    "test:public": "BREAKAGE_CLI_ENTRYPOINT=./src/breakage.x.ts bun test -- ./tests/public",
+    "test:watch": "BREAKAGE_CLI_ENTRYPOINT=./src/breakage.x.ts bun test --watch -- ./__tests__ ./tests/public"
   }
 }