Conversation
WalkthroughProject-wide pre-release version bump from 3.0.0-alpha.33 to 3.0.0-beta.1 across many package.json files; one script update adds --follow-symlinks to the VSCode extension packaging command. No other code, dependencies, or public APIs changed. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Poem
📜 Recent review detailsConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro 💡 Knowledge Base configuration:
You can enable these sources in your CodeRabbit configuration. 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
⏰ 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). (2)
✨ Finishing Touches🧪 Generate unit tests
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. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. CodeRabbit Commands (Invoked using PR/Issue comments)Type Other keywords and placeholders
Status, Documentation and Community
|
There was a problem hiding this comment.
Pull Request Overview
This PR updates the version number across all packages from 3.0.0-alpha.33 to 3.0.0-beta.1, marking the transition from alpha to beta release phase. This is a coordinated version bump across the entire monorepo to maintain consistency.
Key changes:
- Version bump from alpha.33 to beta.1 across all packages
- Addition of
--follow-symlinksflag to VSCode package command
Reviewed Changes
Copilot reviewed 17 out of 17 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
| package.json | Root package version update |
| packages/cli/package.json | CLI package version update |
| packages/common-helpers/package.json | Common helpers package version update |
| packages/create-zenstack/package.json | Create zenstack package version update |
| packages/dialects/sql.js/package.json | SQL.js dialect package version update |
| packages/eslint-config/package.json | ESLint config package version update |
| packages/ide/vscode/package.json | VSCode extension package script update |
| packages/language/package.json | Language package version update |
| packages/runtime/package.json | Runtime package version update |
| packages/sdk/package.json | SDK package version update |
| packages/tanstack-query/package.json | TanStack Query package version update |
| packages/testtools/package.json | Test tools package version update |
| packages/typescript-config/package.json | TypeScript config package version update |
| packages/vitest-config/package.json | Vitest config package version update |
| packages/zod/package.json | Zod package version update |
| samples/blog/package.json | Blog sample package version update |
| tests/e2e/package.json | E2E tests package version update |
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
|
Claude finished @ymc9's task —— View job PR Review: Version Bump to BetaReviewing this PR for code quality, potential issues, and best practices. Todo List:
Comprehensive Review Results✅ Code Quality & Best PracticesExcellent execution of version bump:
📦 Enhancement: VSCode Extension FixFile: - "vscode:package": "pnpm build && vsce package --no-dependencies"
+ "vscode:package": "pnpm build && vsce package --no-dependencies --follow-symlinks"Analysis: This addition brings consistency with the 🔒 Security Considerations
⚡ Performance Considerations
🧪 Test Coverage RecommendationsWhile this PR is low-risk, consider:
📋 Minor Observations
Final Assessment✅ APPROVED - This is a well-executed, low-risk version bump that properly transitions the project from alpha to beta phase. The consistency across all packages and the VSCode script enhancement demonstrate good release management practices. |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 4
📜 Review details
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
💡 Knowledge Base configuration:
- MCP integration is disabled by default for public repositories
- Jira integration is disabled by default for public repositories
- Linear integration is disabled by default for public repositories
You can enable these sources in your CodeRabbit configuration.
📒 Files selected for processing (17)
package.json(1 hunks)packages/cli/package.json(1 hunks)packages/common-helpers/package.json(1 hunks)packages/create-zenstack/package.json(1 hunks)packages/dialects/sql.js/package.json(1 hunks)packages/eslint-config/package.json(1 hunks)packages/ide/vscode/package.json(1 hunks)packages/language/package.json(1 hunks)packages/runtime/package.json(1 hunks)packages/sdk/package.json(1 hunks)packages/tanstack-query/package.json(1 hunks)packages/testtools/package.json(1 hunks)packages/typescript-config/package.json(1 hunks)packages/vitest-config/package.json(1 hunks)packages/zod/package.json(1 hunks)samples/blog/package.json(1 hunks)tests/e2e/package.json(1 hunks)
🧰 Additional context used
📓 Path-based instructions (2)
{packages,samples,tests}/**
📄 CodeRabbit inference engine (CLAUDE.md)
Packages are located in
packages/,samples/, andtests/
Files:
packages/dialects/sql.js/package.jsonpackages/zod/package.jsonpackages/runtime/package.jsonpackages/sdk/package.jsonpackages/language/package.jsonpackages/vitest-config/package.jsonpackages/ide/vscode/package.jsonpackages/cli/package.jsonpackages/typescript-config/package.jsonpackages/create-zenstack/package.jsonpackages/common-helpers/package.jsontests/e2e/package.jsonpackages/eslint-config/package.jsonsamples/blog/package.jsonpackages/testtools/package.jsonpackages/tanstack-query/package.json
tests/e2e/**
📄 CodeRabbit inference engine (CLAUDE.md)
E2E tests are in
tests/e2e/directory
Files:
tests/e2e/package.json
🧠 Learnings (1)
📚 Learning: 2025-08-04T08:43:33.161Z
Learnt from: CR
PR: zenstackhq/zenstack-v3#0
File: CLAUDE.md:0-0
Timestamp: 2025-08-04T08:43:33.161Z
Learning: `zenstack generate` compiles ZModel to TypeScript schema (`schema.ts`)
Applied to files:
packages/language/package.json
⏰ 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). (2)
- GitHub Check: build-test (20.x)
- GitHub Check: claude-review
🔇 Additional comments (14)
packages/vitest-config/package.json (1)
4-4: Approve version bump – no3.0.0-alpha.*references remain and all 13 packages are now at3.0.0-beta.1.packages/eslint-config/package.json (1)
3-3: LGTM on prerelease bump.No config changes; safe to merge.
packages/language/package.json (1)
4-4: Language package version bump is correct.No exports/deps changes; build scripts unchanged.
packages/tanstack-query/package.json (1)
3-3: LGTM.Peer deps and exports untouched; only version updated.
packages/create-zenstack/package.json (1)
3-3: LGTM on version bump.CLI metadata and bin mapping unaffected.
package.json (1)
3-3: Approve version bump to 3.0.0-beta.1. Verified every package.json now lists"version": "3.0.0-beta.1"and no leftover3.0.0-alpha.33references remain.packages/common-helpers/package.json (1)
3-3: Package version updated to beta.1 — OK.Monorepo workspace ranges unchanged; no API or script impact.
packages/testtools/package.json (1)
3-3: Testtools version bump is consistent — OK.Peer ranges unchanged; no publish/runtime risk from this change.
tests/e2e/package.json (1)
3-3: E2E package version bump is fine.Private package; no effect on registry publishing.
packages/typescript-config/package.json (1)
3-3: Typescript config package moved to beta.1 — OK.No functional fields touched.
packages/cli/package.json (1)
6-6: Version bump to 3.0.0-beta.1 looks good.
No functional changes; safe metadata update.packages/zod/package.json (1)
3-3: Version set to 3.0.0-beta.1 — OK.
Package remains private; no publish risk.packages/runtime/package.json (1)
3-3: Runtime version bump approved.
Peers remain on catalog/workspace; no cross-version conflicts expected.packages/dialects/sql.js/package.json (1)
3-3: Dialect package version bump LGTM.
No export/script changes; safe.
|
Claude finished @ymc9's task —— View job PR Review: Version Bump to BetaReviewing this PR for code quality, potential issues, and best practices. Todo List:
Comprehensive Review Results✅ Code Quality & Best PracticesExcellent execution of version bump:
📦 Enhancement: VSCode Extension FixFile: - "vscode:package": "pnpm build && vsce package --no-dependencies"
+ "vscode:package": "pnpm build && vsce package --no-dependencies --follow-symlinks"Analysis: This addition brings consistency with the 🔒 Security Considerations
⚡ Performance Considerations
🧪 Test Coverage RecommendationsWhile this PR is low-risk, consider:
📋 Minor Observations
Final Assessment✅ APPROVED - This is a well-executed, low-risk version bump that properly transitions the project from alpha to beta phase. The consistency across all packages and the VSCode script enhancement demonstrate good release management practices. |
1 participant
Summary by CodeRabbit