fix(ci,backend,docker): ensure migration files present and included in CI and build outputs#24
Open
cto-new[bot] wants to merge 1 commit intodevelopfrom
Conversation
…ed in builds CI sometimes failed due to missing migration files in the backend or Docker context. This change ensures that required migration artifacts are always present and correctly included in both CI checks and release/Docker artifacts. - Adds an explicit check-migration-files script to verify migration files exist - Adds this check to all backend CI jobs for faster, clearer feedback if missing - Dockerfile now explicitly copies migration directory and ormconfig.js to ensure migrations are present in Docker images/releases - Minimizes future risk of DB drift by surfacing migration file absence early No breaking changes; expected to reduce CI false-negatives and production risk.
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
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
This PR ensures that database migration files are always present and included at build and in CI, preventing deployment and CI failures due to missing artifacts.
Details
check-migration-filesscript that verifies all expected migration files exist in the backendmigration/directory and backendormconfig.jsinto Docker imagesWarning: Task VM test is not passing, cto.new will perform much better if you fix the setup