Repository navigation
fix: skip pre-deploy checks in projects without PGlite support - #145
Merged
Merged
Conversation
Projects from the v1 template have no PGlite support in src/orm.config.ts, so migrate verify and test smoke failed at the schema step and blocked the in-browser deploy (prod svc 52). They now pass as skipped and say why.
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.
v1-template projects (e.g. prod svc 52) have no PGlite support in
src/orm.config.ts, sotest smoke/migrate verifyfailed at schema:sync ("Wrong driver: pglite") and blocked the in-browser deploy. They now return ok with a singleskippedstep that says why.Verified: svc 52's saved code (0.41.1 generate + install, 0 tsc errors) → smoke reports skipped and passes; Customer CRM (current template) still runs and passes. 3 new unit tests; 373 tests, lint 0 errors.