You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+13Lines changed: 13 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,6 +6,19 @@ The format follows Keep a Changelog and the version numbers follow Semantic Vers
6
6
7
7
## [Unreleased]
8
8
9
+
## [0.4.4] - 2026-03-31
10
+
11
+
### Added
12
+
13
+
- Added `devforge doctor`, a machine-level readiness command that inspects Node.js, package managers, Corepack, Bun, Playwright browser installs, Git, Docker, and SSH setup before scaffold generation.
14
+
- Added `devforge init --preflight-only` so users can run the same stack-aware readiness checks as the normal init flow without writing project files yet.
15
+
- Added a packed-tarball smoke script and CI gate so DevForge now validates the shipped npm artifact in addition to the source checkout.
16
+
17
+
### Changed
18
+
19
+
- Centralized machine-remediation commands into a shared module so `doctor`, preflight output, and runtime guidance all recommend the same OS-specific fix commands.
20
+
- Improved CLI help and repository docs to explain the new preflight workflow, `doctor`, and the difference between source smoke checks and packed-artifact smoke checks.
-`npm run check` is the main contributor safety command because it combines linting, typechecking, tests, and build verification.
103
117
-`npm run docs:changelog` refreshes the GitHub Pages changelog page from `CHANGELOG.md`.
104
118
-`npm run smoke` verifies a non-interactive scaffold run end to end.
119
+
-`npm run smoke:packed` packs the actual npm tarball, installs it into a temp directory, and verifies the published artifact shape instead of only the source checkout.
105
120
-`npm run runtime:matrix -- --scenario ...` installs, builds, and verifies generated projects so the scaffold output is tested as a product, not just as source code.
- Added `devforge doctor`, a machine-level readiness command that inspects Node.js, package managers, Corepack, Bun, Playwright browser installs, Git, Docker, and SSH setup before scaffold generation.
17
+
- Added `devforge init --preflight-only` so users can run the same stack-aware readiness checks as the normal init flow without writing project files yet.
18
+
- Added a packed-tarball smoke script and CI gate so DevForge now validates the shipped npm artifact in addition to the source checkout.
19
+
20
+
### Changed
21
+
22
+
- Centralized machine-remediation commands into a shared module so `doctor`, preflight output, and runtime guidance all recommend the same OS-specific fix commands.
23
+
- Improved CLI help and repository docs to explain the new preflight workflow, `doctor`, and the difference between source smoke checks and packed-artifact smoke checks.
-`npm run test` runs focused regression tests for prompting, normalization, generator output, changelog rendering, and runtime-matrix coverage.
40
42
-`npm run build` compiles the CLI to `dist/`, which mirrors what npm users receive.
41
43
-`npm run check` is the primary contributor gate because it runs lint, types, tests, and build verification together.
44
+
-`npx --yes @ali-dev11/devforge@latest doctor` checks the local machine for the tool and runtime prerequisites that commonly break first-run scaffolds.
42
45
-`npm run docs:changelog` keeps the GitHub Pages changelog synchronized with `CHANGELOG.md`.
43
46
-`npm run smoke` verifies a fast end-to-end scaffold run without interactive prompts.
47
+
-`npm run smoke:packed` verifies the built npm tarball by installing the packed artifact into a temp directory and running the shipped CLI from there.
44
48
-`npm run runtime:matrix -- --scenario ...` validates generated projects as products by installing, building, and checking runtime behavior for representative stacks.
45
49
46
50
## Working On Generated Scaffolds
47
51
48
52
- Prefer `npm run smoke` for quick CLI sanity checks.
53
+
- Run `npx --yes @ali-dev11/devforge@latest init --preflight-only` when you want stack-aware readiness checks without writing a new project yet.
49
54
- Use `npm run runtime:matrix` when changing templates, prompts, package-manager behavior, or generated runtime surfaces.
55
+
- Use `npm run smoke:packed` when changing the package entrypoints, published files, CLI dispatch, or install-time behavior.
50
56
- If you touch microfrontend templates, validate the generated `dev` workflow, not just build output.
51
57
- If you touch docs or release notes, rerun `npm run docs:changelog`.
0 commit comments