changelog.md

title	Changelog

Changelog

Track what changed in DevForge CLI across releases, including scaffolding behavior, runtime verification improvements, and release automation updates.

• GitHub Releases
• Repository Changelog

[0.5.1] - 2026-04-09

Added

• Added a deployment profile layer that records provider-specific build commands, start commands, ports, health paths, generated files, secrets, and environment-variable expectations for verified scaffold pairs.
• Added Render deployment baselines for verified react-vite frontend apps and express, fastify, and hono backend APIs, including generated render.yaml output and deploy workflow guidance.
• Added Railway deployment baselines for verified nextjs frontend apps and express, fastify, and hono backend APIs, including generated railway.toml output and deploy workflow guidance.
• Added deployment-profile regression coverage, provider-specific generator assertions, runtime-matrix scenarios for frontend-nextjs-railway and backend-fastify-render, and packed-artifact smoke coverage for deployment-target upgrades.
• Added deployment-aware .env.example, README, architecture, and getting-started outputs so generated projects surface provider env vars and deployment expectations alongside local run commands.
• Added end-to-end runtime coverage for capability-heavy NestJS + Fastify + pnpm + Jest backends and React Chrome extension + pnpm + Jest scaffolds so non-default package-manager and test-runner paths are exercised as generated projects.

Changed

• Expanded deployment-aware scaffold docs and CLI guidance so generated projects now explain build commands, start commands, health checks, provider secrets, and expected environment variables for the selected deployment target.
• Updated devforge upgrade so deployment target changes can remove stale managed provider files such as vercel.json, netlify.toml, render.yaml, railway.toml, and docker-compose.yml when those files still match a previous generated baseline.
• Updated generated backend and Next.js runtime commands to bind to deployment-friendly hosts, which makes managed hosting baselines more usable without manual edits.
• Expanded CI and packed-artifact smoke coverage so the shipped npm package now exercises deployment-target refresh against Render, while source CI validates the new Railway and Render runtime scenarios directly.
• Clarified backend capability prompts and generated guidance so authentication, database, ORM, Redis, Swagger, and WebSocket selections are described as starter baselines unless the scaffold fully wires them.

Fixed

• Fixed deployment-target support so verified managed-hosting targets are exercised by the runtime matrix and packed npm smoke path instead of relying only on unit-level generation checks.
• Fixed deployment upgrade behavior for users switching providers by cleaning up obsolete managed deployment files even when the stored project plan has already been normalized to the new target.
• Fixed generated Jest example tests so TypeScript projects include explicit Jest type references during build and typecheck instead of depending on missing ambient globals.
• Fixed generated Jest configs so TypeScript 6 based scaffolds ignore the known ts-jest deprecation codes that would otherwise break pnpm run test on browser-oriented projects.
• Fixed NestJS Fastify scaffolds so the generated server bootstrap uses @nestjs/platform-fastify instead of falling back to the default Express driver.
• Fixed runtime-matrix package-manager installs so pnpm and yarn scenarios can run through Corepack when the package manager is not globally installed.
• Fixed the runtime matrix to cover the exact NestJS + Fastify + pnpm + Jest backend path and React Chrome extension + pnpm + Jest path that had previously escaped end-to-end validation.
• Fixed runtime-matrix pnpm fallbacks on CI runners by switching the no-global-pnpm path away from Corepack key resolution and onto an npm-backed pnpm invocation.

[0.5.0] - 2026-04-02

Added

• Added devforge init --preset <name-or-path> with built-in presets for frontend-app, backend-api, fullstack-app, and chrome-extension, plus support for local preset JSON files.
• Added devforge upgrade to refresh DevForge-managed docs, workflows, AI rules, deployment files, and core tooling surfaces from .devforge/project-plan.json.
• Added deployment-target support for verified scaffold pairs: react-vite frontend apps can target Vercel or Netlify, nextjs frontend apps can target Vercel, and express, fastify, and hono backend APIs can target Docker Compose.
• Added target-specific deployment generation including vercel.json, netlify.toml, docker-compose.yml, and manual deploy workflow examples when GitHub Actions are enabled.
• Added regression coverage for presets, upgrade behavior, deployment-target normalization, deployment artifact generation, and runtime-matrix deployment scenarios.

Changed

• Extended the packed npm smoke path so it now validates preset-driven init, upgrade, deployment-target refresh, and managed feature addition from the packed tarball.
• Updated generated project docs to explain presets, devforge upgrade, deployment targets, and the managed-surface lifecycle.
• Added managed markers to generated docs, workflows, AI rule files, and other comment-friendly managed surfaces so plan-driven upgrades can safely refresh those files later.
• Updated generated deployment-oriented Dockerfiles to use production-style start commands for Docker Compose baselines instead of defaulting to dev-mode entrypoints.

Fixed

• Fixed upgrade behavior for plan changes by allowing managed-marker files such as README and generated docs to refresh even when the stored project plan changes between runs.
• Fixed the generated deployment matrix so verified deployment targets are actually exercised by repository CI instead of existing only in unit-level checks.
• Fixed generator-side source sanitization for user-controlled strings embedded into generated TypeScript and JavaScript files, including Remix metadata exports and CLI/runtime metadata payloads.
• Fixed runtime-matrix loopback HTTP verification so it no longer relies on fetch-based downloads for local readiness checks, which removes the insecure-download CodeQL finding without weakening scenario coverage.

[0.4.5] - 2026-04-01

Added

• Added config-as-code support with devforge init --config <path> so saved scaffold plans can be replayed non-interactively.
• Added devforge init --save-config [path] so interactive runs can emit a reusable devforge.config.json file for teams and future scaffolds.
• Added config regression coverage that round-trips normalized plans through saved config files and verifies scaffold output stays deterministic.
• Added devforge add <feature> for managed post-scaffold updates, with initial support for testing, docker, github-actions, and ai-rules.

Changed

• Extended CLI help, generated project docs, and repository docs to explain the new config-driven workflow and how reusable scaffold plans fit alongside interactive prompts.
• Routed config-driven runs through the same environment defaults and normalization flow as interactive runs so support-matrix rules stay consistent across both entrypoints.
• Extended the packed npm-artifact smoke path so it now exercises devforge add docker after scaffold creation, verifying the shipped CLI can perform managed post-scaffold updates.

Fixed

• Made post-scaffold feature application metadata-driven by reading .devforge/project-plan.json, which avoids stack guessing and keeps repeated devforge add runs idempotent.
• Fixed devforge init --save-config with the default in-project config path so the saved config no longer makes the target directory look non-empty before generation.
• Tightened devforge add guidance and managed-file updates so repeated runs avoid unnecessary churn and generated README content stays aligned with newly added managed features.

[0.4.4] - 2026-03-31

Added

• 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.
• 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.
• Added a packed-tarball smoke script and CI gate so DevForge now validates the shipped npm artifact in addition to the source checkout.

Changed

• Centralized machine-remediation commands into a shared module so doctor, preflight output, and runtime guidance all recommend the same OS-specific fix commands.
• 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.

[0.4.3] - 2026-03-27

Fixed

• Fixed generated Jest setups for TypeScript projects to use runnable CommonJS config files with ts-jest transforms, so scaffolds no longer require ts-node just to load jest.config.
• Fixed scaffold creation on unsupported local Node versions by skipping dependency installation before partial native installs can happen and by printing explicit version-switch and reinstall guidance instead of misleading run commands.
• Stopped offering happy-dom with Jest and normalize unsupported test environment selections to supported fallbacks.

[0.4.2] - 2026-03-26

Added

• Added OS-aware post-create guidance that detects missing local prerequisites such as package managers, Playwright browsers, Git, Docker, and custom Node mismatches, then prints exact next-step install commands for macOS, Linux, and Windows.
• Added generated README and getting-started guidance that mirrors the CLI output with install, run, build, check, and stack-specific follow-up commands.
• Added exhaustive compatibility-matrix regression coverage across supported stack, tooling, testing, node-strategy, and template combinations.

Changed

• Centralized stack capability rules so prompts, normalization, generated docs, and post-create guidance all share the same support matrix.
• Tightened prompt flows to hide unsupported combinations instead of presenting them and correcting them later.
• Restricted Bun support to verified stack paths and tailored generated command guidance to the selected package manager.

Fixed

• Fixed Remix scaffolds to include the CLI/dev dependencies required for npm run dev, pnpm run dev, yarn dev, and bun run dev style workflows.
• Fixed Tailwind-enabled Remix scaffolds to use the Vite Tailwind integration path instead of the PostCSS-only setup, which resolves the Bun production-build failure in the runtime matrix.
• Fixed strict ESLint scaffolds so typed rules no longer run against config files such as eslint.config.js.
• Stopped offering invalid combinations such as microfrontend architecture outside the microfrontend intent, NestJS with JavaScript, RTK Query without compatible Redux state, and ORMs when no database is selected.

[0.4.1] - 2026-03-26

Changed

• Trimmed the published npm package so CI-only runtime-matrix binaries are no longer shipped in the public tarball.

Fixed

• Replaced runtime package metadata reads with generated constants so the published CLI no longer depends on a runtime package.json asset lookup, which reduces scanner and bundle-analysis noise for the npm package.

[0.4.0] - 2026-03-26

Added

• Added repository hardening files and workflows: CODEOWNERS, Dependabot configuration, a pull-request dependency review workflow, and GitHub release artifact attestations.
• Added generated README and getting-started command guides that explain what each common command does and why it matters.
• Added a dedicated prompt reference page so users can understand what each CLI question changes and why DevForge asks it.

Changed

• Refreshed the public README and documentation site with clearer positioning, stronger command explanations, and clearer guidance around default versus optional tooling.
• Made Husky and Commitlint opt-in defaults, while keeping ESLint and Prettier enabled as the baseline quality setup.
• Narrowed generated microfrontend strategy support to the currently implemented Vite federation flow so prompts and normalization no longer imply unsupported runtime behavior.

Fixed

• Reworked generated microfrontend workspaces to use a federation-aware host and remote setup with stable ports, remote entry exposure, and a dev workflow that no longer races three generic Vite apps against each other.
• Improved installer UX by surfacing explicit progress steps before dependency installation and git setup begin.
• Added pnpm build-approval hints for browser-oriented scaffolds so common esbuild installs no longer stop at an approval warning on fresh pnpm setups.
• Updated generated Tailwind Vite scaffolds to use the current Tailwind package integration instead of writing unprocessed @tailwind directives without the required plugin setup.
• Added explicit least-privilege GITHUB_TOKEN permissions to the CI workflow so CodeQL no longer flags the runtime matrix jobs for inheriting repository-default token access.
• Tightened local runtime-matrix HTTP probes so they verify successful startup without downloading page bodies over loopback HTTP, resolving the CodeQL insecure-download alert while keeping stack verification intact.

[0.3.4] - 2026-03-26

Changed

• Improved architecture labels so backend and other non-frontend flows explain what simple, modular, and monorepo mean more clearly during prompting.
• Added a real-time file generation progress bar during scaffold creation so the CLI shows visible progress after printing the target directory.

Fixed

• Prevented incompatible backend selections by filtering out Drizzle when MongoDB is chosen and by normalizing any Drizzle + MongoDB plan back to a supported setup.
• Stopped generating .nvmrc for LTS and Latest Node strategies, avoiding broken version-manager lookups like lts-latest on systems that cannot resolve that alias.
• Hardened dependency installation for yarn and pnpm by using Corepack when available and by keeping package-manager caches local to the generated project.
• Removed stale lockfiles from other package managers before installation so the selected package manager stays authoritative after retries or partial runs.

[0.3.3] - 2026-03-26

Added

• Added a tag-driven GitHub release workflow that validates the repo, extracts release notes from CHANGELOG.md, and publishes a GitHub Release with the packaged npm artifact attached.
• Added a reusable changelog rendering script for release notes and GitHub Pages documentation output.

Changed

• Refreshed the public README with clearer product positioning, benefits, starter-surface details, and docs and release links.
• Expanded the documentation site with stronger product messaging and a dedicated changelog page.
• Updated the Pages workflow to render the changelog page directly from CHANGELOG.md during site builds.

[0.3.2] - 2026-03-26

Fixed

• Hardened generated runtime-matrix process shutdown by terminating the full spawned process group for preview and start commands, which prevents Linux CI jobs from lingering after verification logs show completion.

[0.3.1] - 2026-03-26

Changed

• Reduced CI runner pressure by grouping generated runtime scenarios into a smaller set of runtime-matrix jobs instead of spawning one hosted-runner job per scenario.
• Made generated runtime verification wait for repository validation to pass before consuming matrix capacity, so bad commits fail faster and do not queue unnecessary stack jobs.
• Updated this repository and generated project GitHub Actions workflows to use newer actions/checkout and actions/setup-node releases.

Fixed

• Added workflow-level concurrency cancellation so superseded pushes stop older CI runs instead of leaving stale jobs queued behind newer commits.

[0.3.0] - 2026-03-26

Added

• Added a generated-project runtime matrix runner that scaffolds representative stacks, installs dependencies, builds them, and verifies real runtime surfaces or production artifacts.
• Added a GitHub Actions matrix job for generated stack verification alongside the existing repository validation job.
• Added regression coverage that enforces runtime-matrix coverage across every primary project intent and every backend framework surface.

Changed

• Raised generated frontend and extension project engine declarations to match the current Vite-family toolchain requirements.
• Documented the local runtime-matrix workflow in contributor docs and development docs.

Fixed

• Added Node compatibility warnings when users choose a custom Node version that is too old for the selected frontend-oriented scaffold.
• Added Node type definitions to generated TypeScript configs so backend, fullstack, and CLI projects build cleanly when they reference process.
• Tightened the runtime verifier so CLI JSON checks execute the built binary directly instead of parsing npm wrapper output.
• Fixed generated Next.js projects to include Next-specific type declarations and tsconfig settings so app-directory CSS imports typecheck during production builds.
• Fixed generated fullstack React plus API projects to compile server code through a dedicated server tsconfig instead of typechecking browser entrypoints with NodeNext emit settings.
• Fixed generated NestJS projects to enable decorator compiler options required for controller methods.
• Added a no-op build script for JavaScript backend scaffolds so install/build/run verification stays consistent across backend language choices.
• Relaxed frontend runtime probes to validate successful startup instead of waiting for client-rendered HTML content that only appears after hydration.
• Fixed Nuxt runtime verification to start the built Nitro server directly instead of passing unsupported preview arguments.

[0.2.3] - 2026-03-25

Added

• Generated richer starter surfaces across the supported intents: frontend apps now render a project-details page, backend APIs expose structured project metadata from / and /health, CLI scaffolds print project info and support --json, Chrome extensions show a detailed popup and log extension metadata, and microfrontend host/remote apps identify their role and generation source.
• Added regression coverage for starter surfaces across every supported intent.

Changed

• Expanded the scaffold audit coverage so every intent now emits a clear primary experience surface instead of only a minimal placeholder.
• Threaded DevForge package metadata through generated outputs so new projects show the creator, package name, and CLI version consistently.

Fixed

• Corrected stale generated starter metadata by sourcing generator identity from the real CLI package instead of duplicating hardcoded values.
• Tightened the microfrontend host/remote starter content so those apps no longer look like generic workspace frontends.

[0.2.2] - 2026-03-25

Changed

• Split the interactive flow into core decisions and optional advanced sections so users can keep recommended defaults for metadata, frontend libraries, backend capabilities, testing, AI rules, and tooling without answering every detail prompt.
• Skipped one-option frontend prompts automatically for constrained flows such as microfrontend scaffolds.
• Expanded default AI rule selection to the full stack-relevant category set when users keep the recommended configuration.

Fixed

• Reset intent-specific defaults when users switch project type during prompting, preventing stale frontend-app defaults from leaking into landing page, backend API, chrome extension, and other flows.
• Ensured backend and testing defaults remain valid when optional advanced questions are skipped, including a safe default adapter for NestJS.

[0.2.1] - 2026-03-25

Fixed

• Made AI rule category prompts stack-aware so frontend-only flows no longer offer backend rules.
• Filtered invalid AI rule categories out of normalized plans for resume, seed, and compatibility-adjusted flows.
• Added regression coverage for rule-category availability across landing page, chrome extension, and other intent-specific paths.

[0.2.0] - 2026-03-25

Fixed

• Prevented interactive prompt crashes when switching from default frontend setup to backend-oriented project flows.
• Restricted architecture choices by project intent so incompatible combinations such as backend plus microfrontend are no longer offered.
• Added safer default select handling and regression coverage for backend and non-frontend prompt paths.
• Added the required packageManager metadata to generated workspace roots so TurboRepo can resolve workspaces correctly.
• Fixed generated fullstack scripts to honor the selected package manager instead of hardcoding npm.
• Fixed workspace and microfrontend scaffolds to generate local app tsconfig and test config files where needed.
• Prevented generated output from writing duplicate paths, escaping the target directory, or targeting an existing file path as a directory.
• Fixed CLI version output so --version stays aligned with package.json.

Changed

• Renamed the npm package to @ali-dev11/devforge.
• Updated user-facing install and CLI examples to use the shorter package name.
• Added release scripts for patch, minor, and major version bumps with pre-release validation.
• Normalized microfrontend scaffolds to the currently supported React (Vite) client-rendered setup and removed the stray default apps/web package from microfrontend outputs.

[0.1.0] - 2026-03-25

Added

• Initial public-ready DevForge CLI foundation
• Added production repo setup with lint, CI, typecheck, smoke workflow, and package exports
• Expanded repository documentation and generated-project documentation
• Improved generated scaffold setup scripts and baseline project docs
• Added MIT licensing, npm publishing documentation, GitHub Pages docs setup, and repository community health files