Conversation
|
Warning Rate limit exceeded@ymc9 has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 15 minutes and 15 seconds before requesting another review. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. 📒 Files selected for processing (3)
📝 WalkthroughWalkthroughThis PR adds a CONTRIBUTING.md, updates README.md content and links, updates root package.json scripts, and bumps package versions across the monorepo from 3.0.0-beta.34 to 3.0.0. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes
Possibly related PRs
Poem
Pre-merge checks and finishing touches✅ Passed checks (3 passed)
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 |
|
Claude finished @ymc9's task —— View job Pull Request Review - Version 3.0.0 BumpI've reviewed this pull request for the version bump from Todo List:
🎯 Review SummaryThis is a clean and well-executed version bump that properly graduates ZenStack from beta to stable release. ✅ Code Quality & Best PracticesExcellent consistency across the monorepo:
✅ Semantic Versioning CompliancePerfect adherence to SemVer:
✅ Dependency ManagementWell-structured dependency approach:
✅ Security & CompatibilityNo security concerns identified:
🔍 Specific ObservationsRoot package.json ( - "version": "3.0.0-beta.34",
+ "version": "3.0.0",All workspace packages follow the same pattern, for example:
Sample projects updated consistently (
📋 Test CoverageNote: This is a version bump only, so functional testing isn't applicable. However, consider:
🚀 RecommendationAPPROVE - This is a textbook example of a proper version bump for a monorepo stable release. The changes are:
This PR successfully graduates ZenStack v3 from beta to stable! 🎉 |
There was a problem hiding this comment.
Pull request overview
This PR bumps the version from 3.0.0-beta.34 to 3.0.0 across the entire monorepo, releasing the stable 3.0.0 version.
- Removes the beta pre-release identifier from all package versions
- Updates 24 package.json files consistently
- Covers all packages, samples, tests, and configuration packages in the monorepo
Reviewed changes
Copilot reviewed 23 out of 23 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
| package.json | Root package version updated to 3.0.0 |
| packages/auth-adapters/better-auth/package.json | Better Auth adapter version bumped to stable |
| packages/cli/package.json | CLI package version bumped to stable |
| packages/clients/tanstack-query/package.json | TanStack Query client version bumped to stable |
| packages/common-helpers/package.json | Common helpers package version bumped to stable |
| packages/config/eslint-config/package.json | ESLint config version bumped to stable |
| packages/config/typescript-config/package.json | TypeScript config version bumped to stable |
| packages/config/vitest-config/package.json | Vitest config version bumped to stable |
| packages/create-zenstack/package.json | Project scaffolding tool version bumped to stable |
| packages/language/package.json | Language specification package version bumped to stable |
| packages/orm/package.json | ORM package version bumped to stable |
| packages/plugins/policy/package.json | Policy plugin version bumped to stable |
| packages/schema/package.json | Schema package version bumped to stable |
| packages/sdk/package.json | SDK package version bumped to stable |
| packages/server/package.json | Server package version bumped to stable |
| packages/testtools/package.json | Test tools package version bumped to stable |
| packages/zod/package.json | Zod package version bumped to stable |
| samples/next.js/package.json | Next.js sample version updated to 3.0.0 |
| samples/orm/package.json | ORM sample version updated to 3.0.0 |
| tests/e2e/package.json | E2E tests version updated to 3.0.0 |
| tests/regression/package.json | Regression tests version updated to 3.0.0 |
| tests/runtimes/bun/package.json | Bun runtime tests version updated to 3.0.0 |
| tests/runtimes/edge-runtime/package.json | Edge runtime tests version updated to 3.0.0 |
The version bump is consistent across all packages and follows semantic versioning correctly. No issues were identified in this straightforward release preparation.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
Claude finished @ymc9's task —— View job Pull Request Review - Version 3.0.0 BumpI've reviewed this pull request for the version bump from Todo List:
🎯 Review SummaryThis is a clean and well-executed version bump that properly graduates ZenStack from beta to stable release. ✅ Code Quality & Best PracticesExcellent consistency across the monorepo:
✅ Semantic Versioning CompliancePerfect adherence to SemVer:
✅ Dependency ManagementWell-structured dependency approach:
✅ Security & CompatibilityNo security concerns identified:
🔍 Specific ObservationsRoot package.json ( - "version": "3.0.0-beta.34",
+ "version": "3.0.0",All workspace packages follow the same pattern, for example:
Sample projects updated consistently (
📋 Test CoverageNote: This is a version bump only, so functional testing isn't applicable. However, consider:
🚀 RecommendationAPPROVE - This is a textbook example of a proper version bump for a monorepo stable release. The changes are:
This PR successfully graduates ZenStack v3 from beta to stable! 🎉 |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
🧹 Nitpick comments (1)
CONTRIBUTING.md (1)
12-12: Minor: Consider capitalizing PostgreSQL consistently.For consistency with industry standard naming, consider using "PostgreSQL" instead of "postgres" (lowercase) when referring to the database server.
🔎 Suggested change
-Test cases are run against both SQLite and Postgres. You should have a postgres server (16 or above) running (either natively or via Docker). The default connection is: +Test cases are run against both SQLite and PostgreSQL. You should have a PostgreSQL server (16 or above) running (either natively or via Docker). The default connection is:
📜 Review details
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (25)
CONTRIBUTING.md(1 hunks)README.md(3 hunks)package.json(2 hunks)packages/auth-adapters/better-auth/package.json(1 hunks)packages/cli/package.json(1 hunks)packages/clients/tanstack-query/package.json(1 hunks)packages/common-helpers/package.json(1 hunks)packages/config/eslint-config/package.json(1 hunks)packages/config/typescript-config/package.json(1 hunks)packages/config/vitest-config/package.json(1 hunks)packages/create-zenstack/package.json(1 hunks)packages/language/package.json(1 hunks)packages/orm/package.json(1 hunks)packages/plugins/policy/package.json(1 hunks)packages/schema/package.json(1 hunks)packages/sdk/package.json(1 hunks)packages/server/package.json(1 hunks)packages/testtools/package.json(1 hunks)packages/zod/package.json(1 hunks)samples/next.js/package.json(1 hunks)samples/orm/package.json(1 hunks)tests/e2e/package.json(1 hunks)tests/regression/package.json(1 hunks)tests/runtimes/bun/package.json(1 hunks)tests/runtimes/edge-runtime/package.json(1 hunks)
🧰 Additional context used
🧠 Learnings (9)
📚 Learning: 2025-11-26T01:55:04.540Z
Learnt from: CR
Repo: zenstackhq/zenstack-v3 PR: 0
File: CLAUDE.md:0-0
Timestamp: 2025-11-26T01:55:04.540Z
Learning: Applies to **/*.zmodel : ZModel schema files should define database structure and policies that compile to TypeScript via `zenstack generate`
Applied to files:
CONTRIBUTING.mdREADME.mdpackages/schema/package.jsonpackages/zod/package.jsonpackages/language/package.json
📚 Learning: 2025-11-26T01:55:04.540Z
Learnt from: CR
Repo: zenstackhq/zenstack-v3 PR: 0
File: CLAUDE.md:0-0
Timestamp: 2025-11-26T01:55:04.540Z
Learning: Applies to packages/zenstackhq/orm/**/*.test.{ts,tsx} : ORM package tests should include comprehensive client API tests and policy tests
Applied to files:
CONTRIBUTING.mdREADME.md
📚 Learning: 2025-11-26T01:55:04.540Z
Learnt from: CR
Repo: zenstackhq/zenstack-v3 PR: 0
File: CLAUDE.md:0-0
Timestamp: 2025-11-26T01:55:04.540Z
Learning: Applies to packages/zenstackhq/cli/**/*.test.{ts,tsx} : CLI package tests should focus on action-specific tests for each command
Applied to files:
CONTRIBUTING.md
📚 Learning: 2025-11-26T01:55:04.540Z
Learnt from: CR
Repo: zenstackhq/zenstack-v3 PR: 0
File: CLAUDE.md:0-0
Timestamp: 2025-11-26T01:55:04.540Z
Learning: Applies to ide/vscode/**/{package.json,version.ts} : The VSCode IDE extension package should maintain a different version from other packages to comply with VSCode Marketplace requirements
Applied to files:
packages/config/typescript-config/package.json
📚 Learning: 2025-11-26T01:55:04.540Z
Learnt from: CR
Repo: zenstackhq/zenstack-v3 PR: 0
File: CLAUDE.md:0-0
Timestamp: 2025-11-26T01:55:04.540Z
Learning: Applies to packages/zenstackhq/orm/**/*.{ts,tsx} : Use Kysely as the query builder interface for low-level database queries, avoiding raw SQL when possible
Applied to files:
README.mdpackages/orm/package.json
📚 Learning: 2025-11-26T01:55:04.540Z
Learnt from: CR
Repo: zenstackhq/zenstack-v3 PR: 0
File: CLAUDE.md:0-0
Timestamp: 2025-11-26T01:55:04.540Z
Learning: Applies to packages/zenstackhq/orm/**/*.{ts,tsx} : Implement plugin hooks at ORM, Kysely, and entity mutation levels for query interception and customization
Applied to files:
README.mdpackages/orm/package.json
📚 Learning: 2025-11-26T01:55:04.540Z
Learnt from: CR
Repo: zenstackhq/zenstack-v3 PR: 0
File: CLAUDE.md:0-0
Timestamp: 2025-11-26T01:55:04.540Z
Learning: Database migrations should use Prisma CLI under the hood via ZenStack commands
Applied to files:
README.md
📚 Learning: 2025-11-26T01:55:04.540Z
Learnt from: CR
Repo: zenstackhq/zenstack-v3 PR: 0
File: CLAUDE.md:0-0
Timestamp: 2025-11-26T01:55:04.540Z
Learning: Use `pnpm` with workspaces for package management, pinned to version `pnpm10.12.1`
Applied to files:
package.json
📚 Learning: 2025-11-26T01:55:04.540Z
Learnt from: CR
Repo: zenstackhq/zenstack-v3 PR: 0
File: CLAUDE.md:0-0
Timestamp: 2025-11-26T01:55:04.540Z
Learning: Use Turbo for build orchestration and run `pnpm build`, `pnpm watch`, `pnpm lint`, and `pnpm test` for development tasks
Applied to files:
package.json
🪛 LanguageTool
CONTRIBUTING.md
[grammar] ~12-~12: Ensure spelling is correct
Context: ... SQLite and Postgres. You should have a postgres server (16 or above) running (either na...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~31-~31: As an alternative to the over-used intensifier ‘very’, consider replacing this phrase.
Context: ...# Development workflow ZenStack adopts a very simple development workflow: 1. Changes shou...
(EN_WEAK_ADJECTIVE)
[style] ~107-~107: Consider shortening or rephrasing this to strengthen your wording.
Context: ...the packages in the workspace. Once you make changes to a package and rebuild it, the sample pr...
(MAKE_CHANGES)
🪛 markdownlint-cli2 (0.18.1)
README.md
26-26: Bare URL used
(MD034, no-bare-urls)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)
- GitHub Check: claude-review
- GitHub Check: build-test (20.x, postgresql)
- GitHub Check: build-test (20.x, sqlite)
🔇 Additional comments (28)
samples/orm/package.json (1)
3-3: Version bump looks good!The version update from beta to stable release (3.0.0) is correctly applied.
packages/server/package.json (1)
3-3: Version bump looks good!The version update to 3.0.0 is correctly applied.
tests/runtimes/edge-runtime/package.json (1)
3-3: Version bump looks good!The version update to 3.0.0 is correctly applied.
tests/e2e/package.json (1)
3-3: Version bump looks good!The version update to 3.0.0 is correctly applied.
samples/next.js/package.json (1)
3-3: Version bump looks good!The version update to 3.0.0 is correctly applied.
packages/orm/package.json (1)
3-3: Version bump looks good!The version update to 3.0.0 is correctly applied.
tests/regression/package.json (1)
3-3: Version bump looks good!The version update to 3.0.0 is correctly applied.
packages/common-helpers/package.json (1)
3-3: Version bump looks good!The version update to 3.0.0 is correctly applied.
packages/config/eslint-config/package.json (1)
3-3: LGTM! Version bump to stable release.The version update from beta to stable (3.0.0) is correct and consistent with the release objectives.
packages/clients/tanstack-query/package.json (1)
3-3: LGTM! Version bump to stable release.The version update is consistent with the monorepo-wide release to 3.0.0.
tests/runtimes/bun/package.json (1)
3-3: LGTM! Version bump for test package.The version update is consistent with the stable release.
packages/config/vitest-config/package.json (1)
4-4: LGTM! Version bump to stable release.The version update is correct and consistent.
packages/language/package.json (1)
4-4: LGTM! Version bump for language package.The stable release version is correctly applied to this core language specification package.
packages/sdk/package.json (1)
3-3: LGTM! Version bump for SDK package.The stable release version (3.0.0) is correctly applied to the SDK.
packages/zod/package.json (1)
3-3: LGTM! Version bump to stable release.The version update is consistent with the stable release. Note that this package uses Zod 4.1.0, which aligns with the latest Zod version.
packages/create-zenstack/package.json (1)
3-3: LGTM! Version bump for create-zenstack CLI.The stable release version is correctly applied to this user-facing scaffolding tool.
packages/plugins/policy/package.json (1)
3-3: Version bump to stable release looks good.The version update from beta to 3.0.0 is consistent with the stable release process.
packages/auth-adapters/better-auth/package.json (1)
3-3: LGTM!Version bump aligns with the stable 3.0.0 release.
package.json (3)
3-3: Version bump to 3.0.0 is appropriate.Transitioning from beta to stable release.
12-14: Convenient test scripts for different database providers.The new test scripts provide a clean way to test against SQLite and PostgreSQL separately, which is valuable for debugging database-specific issues.
19-20: Publish scripts correctly updated for stable release.Removing
--tag nextis the right change when publishing a stable version. Thepublish-previewscript appropriately retains its custom registry while also dropping the tag.packages/cli/package.json (1)
6-6: Version updated consistently.The CLI package version aligns with the monorepo release.
packages/testtools/package.json (1)
3-3: LGTM!Version bump is consistent with the stable release.
packages/schema/package.json (1)
3-3: Version bump looks good.Consistent with the 3.0.0 stable release.
packages/config/typescript-config/package.json (1)
3-3: Version bump applied consistently.Even though this is a private package, maintaining version consistency across the monorepo is good practice.
CONTRIBUTING.md (1)
1-109: Excellent contributor guidelines document.This is a comprehensive and well-structured guide that covers all essential aspects: prerequisites, test setup, development workflow, project structure, and local testing. It will be valuable for new contributors.
README.md (2)
59-59: Install commands correctly updated for stable release.The commands have been properly updated from
@nextto@latestacross all installation methods, which is appropriate for the stable 3.0.0 release.Also applies to: 67-67, 75-76
85-113: Sponsors and Community sections well-formatted and complete.The new Sponsors and Community sections are properly structured with working links and responsive sponsor/contributor attribution. The section aligns well with project maturity and community engagement as part of the stable release.
|
Claude finished @ymc9's task —— View job Pull Request Review - Version 3.0.0 BumpI've reviewed this pull request for the version bump from Todo List:
🎯 Review SummaryThis is a clean and well-executed version bump that properly graduates ZenStack from beta to stable release. ✅ Code Quality & Best PracticesExcellent consistency across the monorepo:
✅ Semantic Versioning CompliancePerfect adherence to SemVer:
✅ Dependency ManagementWell-structured dependency approach:
✅ Security & CompatibilityNo security concerns identified:
🔍 Specific ObservationsRoot package.json ( - "version": "3.0.0-beta.34",
+ "version": "3.0.0",All workspace packages follow the same pattern, for example:
Sample projects updated consistently (
📋 Test CoverageNote: This is a version bump only, so functional testing isn't applicable. However, consider:
🚀 RecommendationAPPROVE - This is a textbook example of a proper version bump for a monorepo stable release. The changes are:
This PR successfully graduates ZenStack v3 from beta to stable! 🎉 |
|
Claude finished @ymc9's task —— View job Pull Request Review - Version 3.0.0 BumpI've reviewed this pull request for the version bump from Todo List:
🎯 Review SummaryThis is a clean and well-executed version bump that properly graduates ZenStack from beta to stable release. ✅ Code Quality & Best PracticesExcellent consistency across the monorepo:
✅ Semantic Versioning CompliancePerfect adherence to SemVer:
✅ Dependency ManagementWell-structured dependency approach:
✅ Security & CompatibilityNo security concerns identified:
🔍 Specific ObservationsRoot package.json ( - "version": "3.0.0-beta.34",
+ "version": "3.0.0",All workspace packages follow the same pattern, for example:
Sample projects updated consistently (
|
1 participant
Summary by CodeRabbit
Chores
Documentation
✏️ Tip: You can customize this high-level summary in your review settings.