delivery-friction-analyzer 0.12.1 → 0.14.0
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.
|
@@ -28,6 +28,12 @@ It validates:
|
|
|
28
28
|
|
|
29
29
|
CI runs on Node 20 and Node 24 so the advertised `engines.node >=20` floor is exercised before release.
|
|
30
30
|
|
|
31
|
+
## Local Preflight
|
|
32
|
+
|
|
33
|
+
For ordinary PRs, run `npm run preflight` before opening or updating review. It runs the full local test suite and `git diff --check HEAD` so whitespace issues are caught across staged and unstaged tracked changes.
|
|
34
|
+
|
|
35
|
+
For release automation, package metadata, package contents, or publish workflow changes, run `npm run preflight:release`. It runs the focused release-versioning tests, including direct CLI entrypoint coverage, validates the package version is not behind the latest local `v*` release tag, and runs `npm pack --dry-run`.
|
|
36
|
+
|
|
31
37
|
## Release Workflow
|
|
32
38
|
|
|
33
39
|
The release workflow runs on pushes to `main` and skips commits whose subject starts with `Release `.
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "delivery-friction-analyzer",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.14.0",
|
|
4
4
|
"description": "Local GitHub pull request analytics for delivery friction reports.",
|
|
5
5
|
"license": "MIT",
|
|
6
6
|
"type": "module",
|
|
@@ -19,6 +19,8 @@
|
|
|
19
19
|
],
|
|
20
20
|
"scripts": {
|
|
21
21
|
"analyze:github": "node src/cli/analyze-github.js",
|
|
22
|
+
"preflight": "npm test && git diff --check HEAD",
|
|
23
|
+
"preflight:release": "node --test test/release-versioning.test.mjs && node scripts/release-versioning.mjs assert-package-not-behind-latest-tag && npm pack --dry-run",
|
|
22
24
|
"report:fixture": "node src/report/generate-report.js --metrics-summary fixtures/github/mcp-writing/metrics-summary.golden.json --json-out fixtures/github/mcp-writing/reports/friction-report.golden.json --markdown-out fixtures/github/mcp-writing/reports/friction-report.golden.md",
|
|
23
25
|
"test": "node --test"
|
|
24
26
|
},
|
package/release-log.md
CHANGED
|
@@ -2,6 +2,22 @@
|
|
|
2
2
|
|
|
3
3
|
## Unreleased
|
|
4
4
|
|
|
5
|
+
### 2026-06-21 — Local Preflight Commands
|
|
6
|
+
|
|
7
|
+
- What changed: Added `npm run preflight` for ordinary PR checks and `npm run preflight:release` for focused release/package validation, with release automation docs describing when to use each command.
|
|
8
|
+
- Why it matters: Maintainers and agents can catch recurring test, whitespace, release-versioning, and package dry-run issues before opening review.
|
|
9
|
+
- Who is affected: Maintainers preparing ordinary PRs, release automation changes, package metadata changes, package contents changes, or publish workflow changes.
|
|
10
|
+
- Action needed: Optional; run `npm run preflight` before ordinary review and `npm run preflight:release` before release/package review.
|
|
11
|
+
- PR: #51
|
|
12
|
+
|
|
13
|
+
### 2026-06-21 — Maintainer Self-Profile Baseline
|
|
14
|
+
|
|
15
|
+
- What changed: Added a repository self-profile for delivery-friction-analyzer so local self-analysis can classify normal development paths, functional surfaces, workflow context, and Conventional Commit-style PR classes.
|
|
16
|
+
- Why it matters: Maintainers can review future self-analysis with fewer `unknown` classifications before changing process or opening follow-up workflow PRs.
|
|
17
|
+
- Who is affected: Maintainers running local analysis against this repository or reviewing profile validation.
|
|
18
|
+
- Action needed: Optional; rerun local self-analysis with `profiles/delivery-friction-analyzer.json` when validating maintainer workflow changes.
|
|
19
|
+
- PR: #50
|
|
20
|
+
|
|
5
21
|
### 2026-06-20 — Reusable Run Presets
|
|
6
22
|
|
|
7
23
|
- What changed: GitHub analysis can now load local run settings from `--preset` and save reusable settings with `--save-preset` or the interactive setup flow, with explicit CLI flags taking precedence.
|