release(cli): cut v0.2.1#3925
Conversation
📝 WalkthroughWalkthroughThe pull request bumps the CLI package version from Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
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. Review rate limit: 7/8 reviews remaining, refill in 7 minutes and 30 seconds.Comment |
There was a problem hiding this comment.
🧹 Nitpick comments (1)
packages/cli/cli.config.ts (1)
3-3: ⚡ Quick winOptional: prevent future version drift between
package.jsonandcli.config.ts.Right now the version string is duplicated (
packages/cli/package.jsonandpackages/cli/cli.config.ts). Consider derivingVERSIONfrom the package manifest (or generatingcli.config.tsduring build) so future releases can’t accidentally drift.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@packages/cli/cli.config.ts` at line 3, The hard-coded VERSION constant causes duplication; replace the literal const VERSION = "0.2.1" with a derived value read from the package manifest at build/runtime (e.g., import or require the package.json and assign VERSION = packageJson.version) or change the build to generate cli.config.ts embedding the package version; update the symbol VERSION accordingly so it always reflects the package.json version and remove the duplicated string.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Nitpick comments:
In `@packages/cli/cli.config.ts`:
- Line 3: The hard-coded VERSION constant causes duplication; replace the
literal const VERSION = "0.2.1" with a derived value read from the package
manifest at build/runtime (e.g., import or require the package.json and assign
VERSION = packageJson.version) or change the build to generate cli.config.ts
embedding the package version; update the symbol VERSION accordingly so it
always reflects the package.json version and remove the duplicated string.
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: b9cee988-7b97-43ae-a6e5-7b1ef005d646
⛔ Files ignored due to path filters (1)
bun.lockis excluded by!**/*.lock
📒 Files selected for processing (2)
packages/cli/cli.config.tspackages/cli/package.json
Greptile SummaryThis PR cuts the Confidence Score: 5/5Safe to merge — changes are a minimal, consistent version bump across three files with no logic changes. All three changed files are version strings only. The VERSION constant in cli.config.ts, package.json, and bun.lock all agree on 0.2.1. The desktop version in bun.lock (1.7.3) matches apps/desktop/package.json on main. No P1 or P0 issues found. No files require special attention.
|
| Filename | Overview |
|---|---|
| packages/cli/package.json | Version bumped from 0.2.0 to 0.2.1 — straightforward patch release increment, no dependency changes. |
| packages/cli/cli.config.ts | VERSION constant updated from "0.2.0" to "0.2.1", keeping the baked-in SUPERSET_VERSION define in sync with package.json. |
| bun.lock | Lock file reflects CLI version bump (0.2.0→0.2.1) and desktop version (1.7.2→1.7.3); desktop/package.json already reads 1.7.3 on main, so both entries are consistent. |
Flowchart
%%{init: {'theme': 'neutral'}}%%
flowchart TD
A[Merge PR - squash] --> B[Push tag cli-v0.2.1]
B --> C[release-cli.yml fires]
C --> D[Build darwin-arm64 tarball]
C --> E[Build linux-x64 tarball]
C --> F[Build linux-arm64 tarball]
D & E & F --> G[Publish GitHub Release v0.2.1]
G --> H[bump-homebrew.yml updates brew formula]
G --> I[install.sh resolves to v0.2.1]
G --> J[superset update resolves to v0.2.1]
Reviews (1): Last reviewed commit: "release(cli): cut v0.2.1" | Re-trigger Greptile
🧹 Preview Cleanup CompleteThe following preview resources have been cleaned up:
Thank you for your contribution! 🎉 |
Already integrated, superseded by current versions, or net-empty in this fork: superset-sh#3881 superset-sh#3887 superset-sh#3917 superset-sh#3925 superset-sh#3940 superset-sh#3956 superset-sh#3961 superset-sh#3974 superset-sh#4017 superset-sh#4048 superset-sh#4049 superset-sh#4055 superset-sh#4063 superset-sh#4070 superset-sh#4092 superset-sh#4110 superset-sh#4138 superset-sh#4159 superset-sh#4163 superset-sh#4164 superset-sh#4209 superset-sh#4210 superset-sh#4249 superset-sh#4349 superset-sh#4405 superset-sh#4462 superset-sh#4464 superset-sh#4494 superset-sh#4495 superset-sh#4500 superset-sh#4535 superset-sh#4541 superset-sh#4566 superset-sh#4580 superset-sh#4589 superset-sh#4593 superset-sh#4603 superset-sh#4637 superset-sh#4642 superset-sh#4655 superset-sh#4657 superset-sh#4659 superset-sh#4685 superset-sh#4692 superset-sh#4745 superset-sh#4789 superset-sh#4797 superset-sh#4824 superset-sh#4835 superset-sh#4847 superset-sh#4885 superset-sh#4896.
Summary
Patch release. v0.2.0 linux-x64 tarballs crash on
superset startbecause the bundled host-service couldn't findtokenizers.linux-x64-gnu.node. v0.2.1 picks up the fix plus the smoke-test polish + remote-access error message work landed since v0.2.0.What's new since v0.2.0
Release flow
cli-v0.2.1to firerelease-cli.yml— builds darwin-arm64 / linux-x64 / linux-arm64 tarballs in CI on real Linux runners and publishes them as a GitHub Releasebump-homebrew.ymlupdates the brew formula with the new SHAsinstall.shandsuperset updateresolve to the new releaseTest plan
release-cli.ymlsucceeds and produces three tarballscurl -fsSL https://superset.sh/cli/install.sh | bash→superset startbrings up the host service without crashingsuperset updatefrom an existing v0.2.0 install resolves to v0.2.1 and replaces the installSummary by CodeRabbit