breakage 0.8.2 → 0.8.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +8 -8
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -4,14 +4,6 @@ Run yesterday’s tests against tomorrow’s release.
|
|
|
4
4
|
|
|
5
5
|
Command line tooling to detect breaking changes before you ship them.
|
|
6
6
|
|
|
7
|
-
## migrating from break-check
|
|
8
|
-
|
|
9
|
-
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>`.
|
|
10
|
-
|
|
11
|
-
For programmatic use, import `breakage`, `BreakageOptions`, and `BreakageOutcome` from `breakage` in place of `breakCheck`, `BreakCheckOptions`, and `BreakCheckOutcome` from `break-check`.
|
|
12
|
-
|
|
13
|
-
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.
|
|
14
|
-
|
|
15
7
|
## can i use breakage?
|
|
16
8
|
|
|
17
9
|
breakage is a tool for projects where
|
|
@@ -253,3 +245,11 @@ These aliases work alongside the original option names. Configuration file keys
|
|
|
253
245
|
| `--outdir` (schema command) | `--out-dir` |
|
|
254
246
|
|
|
255
247
|
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.
|
|
248
|
+
|
|
249
|
+
## migrating from break-check
|
|
250
|
+
|
|
251
|
+
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>`.
|
|
252
|
+
|
|
253
|
+
For programmatic use, import `breakage`, `BreakageOptions`, and `BreakageOutcome` from `breakage` in place of `breakCheck`, `BreakCheckOptions`, and `BreakCheckOutcome` from `break-check`.
|
|
254
|
+
|
|
255
|
+
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
CHANGED