Skip to content

chore(desktop): bump version to 1.5.8 #3617

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Kitenite merged 1 commit into from
Apr 22, 2026
+1 −1
Merged

chore(desktop): bump version to 1.5.8 #3617

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion apps/desktop/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
"name": "@superset/desktop",
"productName": "Superset",
"description": "The last developer tool you'll ever need",
"version": "1.5.6",
"version": "1.5.8",
Copy link
Copy Markdown
Contributor

@greptile-apps greptile-apps Bot Apr 21, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Version skips 1.5.7

The version jumps directly from 1.5.6 to 1.5.8, skipping 1.5.7. If this is intentional (e.g., 1.5.7 was yanked, reserved, or already published externally), no action is needed. However, if the release script is expected to increment sequentially, this could indicate a misconfiguration or a prior release that wasn't reflected here.

Prompt To Fix With AI 
This is a comment left during a code review.
Path: apps/desktop/package.json
Line: 5

Comment:
**Version skips 1.5.7**

The version jumps directly from `1.5.6` to `1.5.8`, skipping `1.5.7`. If this is intentional (e.g., `1.5.7` was yanked, reserved, or already published externally), no action is needed. However, if the release script is expected to increment sequentially, this could indicate a misconfiguration or a prior release that wasn't reflected here.

How can I resolve this? If you propose a fix, please make it concise.

"main": "./dist/main/index.js",
"resources": "src/resources",
"repository": {
Expand Down
Loading