chore(desktop): bump version to 1.9.9#4745
Conversation
|
Ready to review this PR? Stage has broken it down into 2 individual chapters for you:
Chapters generated by Stage for commit bf3edfb on May 20, 2026 12:13am UTC. |
|
Capy auto-review is paused for this organization because the monthly auto-review limit has been reached. Increase the limit or turn it off in billing settings to resume automatic reviews. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughVersion fields are bumped in two package manifests: desktop app from 1.9.7 to 1.9.9, and host-service from 0.8.7 to 0.8.8. No dependencies, scripts, or other fields are modified. ChangesPackage Version Updates
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly related PRs
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 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. Comment |
Greptile SummaryThis is an automated version-bump PR for the desktop app, raising
Confidence Score: 4/5Safe to merge; the only question is whether the desktop version intentionally skips 1.9.8. Both files contain only version string changes. The host-service bump is a clean sequential increment. The desktop bump skips a version number, which could confuse tooling or regression bisecting if 1.9.8 was never published, but does not affect runtime behavior. apps/desktop/package.json — confirm the 1.9.7 → 1.9.9 skip is intentional.
|
| Filename | Overview |
|---|---|
| apps/desktop/package.json | Desktop app version bumped from 1.9.7 to 1.9.9 — skips 1.9.8, which may be intentional or a release-script artifact |
| packages/host-service/package.json | host-service version bumped from 0.8.7 to 0.8.8 — sequential increment, no issues |
Flowchart
%%{init: {'theme': 'neutral'}}%%
flowchart TD
A[Release Script Triggered] --> B[Bump desktop version]
B --> C{Expected increment?}
C -- "1.9.7 → 1.9.8 (sequential)" --> D[✅ Normal]
C -- "1.9.7 → 1.9.9 (skips 1.9.8)" --> E[⚠️ Version gap — verify intent]
A --> F[Bump host-service version]
F --> G["0.8.7 → 0.8.8 (sequential)"]
G --> H[✅ Normal]
Prompt To Fix All With AI
Fix the following 1 code review issue. Work through them one at a time, proposing concise fixes.
---
### Issue 1 of 1
apps/desktop/package.json:4
**Version skip from 1.9.7 to 1.9.9**
The desktop version jumps from `1.9.7` directly to `1.9.9`, bypassing `1.9.8`. If `1.9.8` was never published this gap could confuse changelog tools, package registries, or anyone bisecting a regression by version number. Was `1.9.8` intentionally skipped or reserved, or is this an artifact of the release script selecting an incorrect next version?
Reviews (1): Last reviewed commit: "chore(desktop): bump version to 1.9.9 (h..." | Re-trigger Greptile
| @@ -2,7 +2,7 @@ | |||
| "name": "@superset/desktop", | |||
| "productName": "Superset", | |||
| "description": "The last developer tool you'll ever need", | |||
There was a problem hiding this comment.
Version skip from 1.9.7 to 1.9.9
The desktop version jumps from 1.9.7 directly to 1.9.9, bypassing 1.9.8. If 1.9.8 was never published this gap could confuse changelog tools, package registries, or anyone bisecting a regression by version number. Was 1.9.8 intentionally skipped or reserved, or is this an artifact of the release script selecting an incorrect next version?
Prompt To Fix With AI
This is a comment left during a code review.
Path: apps/desktop/package.json
Line: 4
Comment:
**Version skip from 1.9.7 to 1.9.9**
The desktop version jumps from `1.9.7` directly to `1.9.9`, bypassing `1.9.8`. If `1.9.8` was never published this gap could confuse changelog tools, package registries, or anyone bisecting a regression by version number. Was `1.9.8` intentionally skipped or reserved, or is this an artifact of the release script selecting an incorrect next version?
How can I resolve this? If you propose a fix, please make it concise.
🧹 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.
Bumps desktop app version to 1.9.9.
This PR was automatically created by the release script.
Summary by cubic
Bumps
@superset/desktopto 1.9.9 and@superset/host-serviceto 0.8.8 for the next desktop release. No functional changes; version-only update.Written for commit bf3edfb. Summary will update on new commits. Review in cubic
Summary by CodeRabbit