chore(desktop): bump version to 1.5.3

[Kitenite]

Bumps desktop app version to 1.5.3.

This PR was automatically created by the release script.

---

Summary by cubic

Updates the @superset/desktop version from 1.5.1 to 1.5.3 to prepare the 1.5.3 desktop patch release. No runtime changes; version metadata only.

^{Written for commit 647c43b. Summary will update on new commits.}

Summary by CodeRabbit

• Chores
  • Updated package version to 1.5.3

[coderabbitai]

📝 Walkthrough

Walkthrough

The @superset/desktop package version in apps/desktop/package.json was incremented from 1.5.1 to 1.5.3. No scripts, dependencies, or public interfaces were modified.

Changes

Cohort / File(s)	Summary
Version Bump apps/desktop/package.json	Incremented package version from 1.5.1 to 1.5.3.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• chore(desktop): bump version to 1.5.1 #3402: Both PRs perform successive version bumps to apps/desktop/package.json, with one setting version to 1.5.1 and the other to 1.5.3.
• chore(desktop): bump version to 1.5.0 #3360: Both PRs modify the same file and version field for apps/desktop in successive version bump operations.
• chore(desktop): bump version to 1.3.1 #2765: Both PRs update the version field in apps/desktop/package.json with identical change type.

Poem

🐰 A hop, a skip, a version rise,
From one-five-one to one-five-three,
The desktop sings with joyful sighs,
Each increment brings harmony! ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely describes the main change: bumping the desktop package version from 1.5.1 to 1.5.3.
Description check	✅ Passed	The description provides essential context (version bump details, auto-generated note), but omits most template sections like Related Issues, Type of Change, Testing, and Additional Notes.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch cedar-tamarind

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[greptile-apps]

Greptile Summary

This is an automated release PR that bumps the @superset/desktop package version to 1.5.3 in apps/desktop/package.json. No logic, dependencies, or scripts were changed — only the "version" field was updated.

• Version field in apps/desktop/package.json updated to "1.5.3"
• Change was generated by the release script, consistent with the repo's release workflow
• No functional impact; purely a metadata change to trigger a new Electron build/release

Confidence Score: 5/5

This PR is safe to merge — it is a single-field version bump with no functional changes.

Only the version field in apps/desktop/package.json was modified from the previous value to 1.5.3. No dependencies, scripts, or logic were altered. The change was produced automatically by the release script, following the established release workflow. There are zero logical, security, or functional risks.

No files require special attention.

Important Files Changed

Filename	Overview
apps/desktop/package.json	Version field bumped from previous release to 1.5.3; no dependency or script changes introduced.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A([Release Script Triggered]) --> B[Bump version in apps/desktop/package.json]
    B --> C[Open PR against main]
    C --> D{PR Review}
    D -->|Approved & Merged| E[CI builds Electron app v1.5.3]
    E --> F[electron-builder --publish always]
    F --> G([New desktop release published])

Loading

_{Reviews (1): Last reviewed commit: "chore(desktop): bump version to 1.5.3" | Re-trigger Greptile}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@apps/desktop/package.json`:
- 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.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: dfc1afbe-8692-4ae8-b6aa-d5d993579697

📥 Commits

Reviewing files that changed from the base of the PR and between 039edf2 and 647c43b.

📒 Files selected for processing (1)

• apps/desktop/package.json

[coderabbitai]

⚠️ 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.

[cubic-dev-ai]

No issues found across 1 file

[github-actions]

🧹 Preview Cleanup Complete

The following preview resources have been cleaned up:

• ⚠️ Neon database branch
• ⚠️ Electric Fly.io app

Thank you for your contribution! 🎉