chore: regenerate stale lite schemas after lite-mode generator change - #2813
Conversation
PR #2794 changed what `zen generate --lite` emits (lite schemas now retain lite attributes instead of stripping all attributes), but the tracked generated schema-lite.ts files were not regenerated. This left the CI working tree dirty after the build step, causing the v3.9.2 publish to fail with ERR_PNPM_GIT_UNCLEAN. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (4)
Included review availability: Your plan provides up to 8 included reviews per hour; 7 remain after this review. 📝 WalkthroughWalkthroughChangesThe schema-lite metadata now records Schema metadata
Estimated code review effort: 2 (Simple) | ~10 minutes Merge Risk: ⚪ Minimal · up to This change refreshes tracked lite schema outputs so generation no longer dirties the working tree; no actionable merge-blocking risk remains after normal checks and review. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Warning There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure. 🔧 ESLint
packages/clients/tanstack-query/test/schemas/basic/schema-lite.tsESLint skipped: missing config or dependency (missing-dependency). The ESLint configuration references a package that is not available in the sandbox. samples/next.js/zenstack/schema-lite.tsESLint skipped: missing config or dependency (missing-dependency). The ESLint configuration references a package that is not available in the sandbox. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary
The v3.9.2 publish run failed with
ERR_PNPM_GIT_UNCLEAN(failed run).Root cause: #2794 changed what
zen generate --liteemits (lite schemas now retain lite attributes such as@default/@updatedAtinstead of stripping all attributes), but the generatedschema-lite.tsfiles tracked in git were not regenerated. Several samples runzen generateas part of theirbuildscript, so CI's build step rewrote these tracked files and left the working tree dirty, causingpnpm publishto refuse to publish.This PR commits the regenerated files. Verified locally that re-running generation on top of this commit produces no diff.
After this lands on
dev, it needs to be merged tomainand the publish workflow re-run to release v3.9.2 (no packages were published by the failed run).Possible follow-up
Consider adding a
git diff --exit-codecheck after the build in the build-test workflow so stale generated files fail PR CI instead of the release.🤖 Generated with Claude Code
Summary by CodeRabbit