generatesaas 3.37.0 → 3.38.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -365,6 +365,7 @@ After all files are processed, run the validation ladder below - every rung. The
|
|
|
365
365
|
|
|
366
366
|
1. **Static gates:**
|
|
367
367
|
- If the project has `packages/mcp-widgets`, run `pnpm -F @repo/mcp-widgets widgets:build` first and commit the rebuilt `widget-documents.generated.ts`: the update never stages that generated module, and the widget drift test fails until it is rebuilt from the updated sources.
|
|
368
|
+
- If the project has `apps/mobile`, run `pnpm --filter @repo/styles mobile-css` and commit `apps/mobile/global.css`: it is generated from the project's own `tooling/styles/theme.css`, so a merged copy carries the template's colours (a dark label on a primary the project made darker, for one) until it is regenerated. The pre-commit hook also regenerates it whenever the commit touches either file.
|
|
368
369
|
- Scan merged files for syntax errors or broken imports
|
|
369
370
|
- Run `pnpm lint`, `pnpm check-types`, and `pnpm test`
|
|
370
371
|
- **Do not rely on the type check alone.** Most packages scope `check-types` to `src/**` and exclude `tests/**`, so a type error introduced into a **test file** during a merge will pass `check-types` silently. If any of your merges landed in a `tests/` file, the test suite is the only gate that exercises it. When in doubt, also type-check the specific merged test files directly (e.g. `npx tsc --noEmit <file>` with the package's tsconfig settings).
|