Skip to content
Merged
Changes from all commits
Commits
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
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.1",
"version": "1.5.3",
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Description: Check git tags and package.json history to verify if 1.5.2 was ever released

# Check if version 1.5.2 exists in git tags
echo "=== Checking for v1.5.2 tag ==="
git tag -l | grep -E "v?1\.5\.2" || echo "No 1.5.2 tag found"

# Check package.json version history
echo -e "\n=== Recent version history in package.json ==="
git log -10 --oneline --all -- apps/desktop/package.json

# Show the actual version changes
echo -e "\n=== Version field changes in last 10 commits ==="
git log -10 --all -p -- apps/desktop/package.json | grep -A1 -B1 '"version"'

Repository: superset-sh/superset

Length of output: 1536


Confirm whether the version increment from 1.5.1 to 1.5.3 was intentional.

The version history shows a direct jump from 1.5.1 to 1.5.3 with no v1.5.2 tag or corresponding commit in the repository. While the skip is confirmed, please verify whether this was intentional (e.g., 1.5.2 was prepared but not released) or if the release script needs adjustment.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@apps/desktop/package.json` at line 5, Check whether the version jump in
apps/desktop/package.json (the "version" field set to "1.5.3") was intentional
by: verifying if a v1.5.2 tag or commit exists in the repo and the
changelog/release notes mention 1.5.2, inspecting the CI/release workflow or
release script that bumps/tags versions for skipped releases, and confirming
with the releaser; if 1.5.2 was omitted unintentionally, either create the
missing v1.5.2 tag/release (with its commit/changelog) or revert/adjust the
"version" in package.json and the release script to the correct next version so
tags, changelog, and package.json stay consistent.

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