Release 0.5.1#13
Merged
Merged
Conversation
…r Render and Railway - Added deployment profile layer for provider-specific configurations. - Introduced Render and Railway deployment baselines for various frontend and backend frameworks. - Expanded documentation and CLI guidance for deployment-aware scaffolds. - Improved upgrade process to clean up obsolete managed provider files. - Fixed various issues related to Jest configurations and runtime matrix coverage.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Introduced a deployment profile layer to capture provider-specific configuration such as build/start commands, ports, health checks, generated files, secrets, and environment variables
Added Render deployment baselines for
react-vitefrontends andexpress,fastify,honobackends with generatedrender.yamland workflow guidanceAdded Railway deployment baselines for
nextjsfrontends andexpress,fastify,honobackends with generatedrailway.tomland workflow guidanceImplemented extensive regression coverage for deployment profiles, provider generators, runtime-matrix scenarios, and packed-artifact smoke tests
Enhanced generated outputs (
.env.example, README, architecture, getting-started) to include deployment-aware configuration and expectationsAdded end-to-end runtime coverage for complex stacks including NestJS + Fastify + pnpm + Jest and React Chrome Extension + pnpm + Jest
Expanded scaffold docs and CLI guidance to include deployment-specific instructions (build/start commands, health checks, secrets, env vars)
Improved
devforge upgradeto clean up stale deployment files (vercel.json,netlify.toml,render.yaml,railway.toml,docker-compose.yml) when switching targetsUpdated runtime commands for backend and Next.js apps to bind to deployment-friendly hosts
Strengthened CI and smoke coverage to validate deployment-target refresh for Render and Railway scenarios
Clarified backend capability prompts to better communicate “starter baseline” vs fully wired features
Fixed deployment-target validation to ensure managed hosting targets are exercised in runtime matrix and smoke tests
Fixed upgrade behavior to properly remove obsolete deployment files when switching providers
Fixed Jest setup for TypeScript projects (type references, ts-jest deprecation handling)
Fixed NestJS Fastify scaffolds to correctly use
@nestjs/platform-fastifyFixed package manager handling in runtime matrix to support pnpm/yarn via Corepack
Fixed missing runtime coverage for specific stack combinations previously not validated end-to-end
Why it changed:
Related Issue
Closes #
Validation
npm run checknpm run smokeif scaffold behavior changedChecklist