chore(desktop): bump version to 0.0.75

[saddlepaddle]

Bumps desktop app version to 0.0.75.

This PR was automatically created by the release script.

Summary by CodeRabbit

• Chores
  • Updated desktop application version.

[coderabbitai]

📝 Walkthrough

Walkthrough

The desktop package version in apps/desktop/package.json is downgraded from 0.0.76 to 0.0.75. This is a single-line configuration change with no other modifications.

Changes

Cohort / File(s)	Summary
Version Update apps/desktop/package.json	Version field downgraded from 0.0.76 to 0.0.75.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~1 minute

Possibly related PRs

• chore(desktop): bump version to 0.0.34 #485: Both PRs modify the version field in apps/desktop/package.json for version management.
• chore(desktop): bump version to 0.0.26 #414: Updates the same version field in apps/desktop/package.json.
• chore(desktop): bump version to 0.0.51 #685: Modifies the version field in apps/desktop/package.json with a different version number.

Poem

🐰 A hop, a skip, a number change!
From 76 down to 75 so strange.
The desktop version takes a rest,
A small rewind—perhaps the best! ✨

🚥 Pre-merge checks | ✅ 3 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description is minimal but lacks required template sections including Related Issues, Type of Change, Testing, and Additional Notes.	Complete the PR description by adding required sections from the template, particularly identifying the change type (chore/refactor) and any testing performed.

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and accurately describes the main change: bumping the desktop app version to 0.0.75, which matches the changeset in package.json.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Merge Conflict Detection	✅ Passed	✅ No merge conflicts detected when merging into main

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

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch 0.75

---

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.}

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@apps/desktop/package.json`:
- Line 5: The package.json "version" field was decreased to "0.0.75" which is a
downgrade; update the "version" value in apps/desktop's package.json (the
"version" key) to the correct, higher semantic version (e.g., change back to
"0.0.76" or the intended new bump) so versions monotonically increase, and then
verify the release script/branch/merge resolution that produced this change to
prevent regressions; ensure the commit message and PR title match the final
"version" value before merging.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Check version history and verify the downgrade claim

echo "=== Git log for apps/desktop/package.json (last 15 commits) ==="
git log --oneline -15 -- apps/desktop/package.json 2>/dev/null || echo "No git history available"

echo -e "\n=== Recent version values from git history ==="
git log -p -10 -- apps/desktop/package.json 2>/dev/null | grep -E '^\+.*"version"|^-.*"version"' | head -20 || echo "Cannot extract version history"

echo -e "\n=== Current branch and version ==="
git branch -v 2>/dev/null || echo "No branch info"
grep '"version"' apps/desktop/package.json

echo -e "\n=== Check if electron-updater is in dependencies ==="
grep -E '"electron-updater"' apps/desktop/package.json && echo "Found electron-updater" || echo "electron-updater not found"

echo -e "\n=== Full version context from current file ==="
sed -n '1,10p' apps/desktop/package.json

Repository: superset-sh/superset

Length of output: 938

---

🏁 Script executed:

#!/bin/bash
# Check version on main branch and earlier commits

echo "=== Version on main branch ==="
git show main:apps/desktop/package.json 2>/dev/null | grep '"version"' || echo "Cannot read main branch"

echo -e "\n=== All commits touching package.json in repository ==="
git log --all --oneline -- apps/desktop/package.json 2>/dev/null | head -20

echo -e "\n=== Detailed diff for the current commit ==="
git show ee420663 -- apps/desktop/package.json 2>/dev/null | head -50

echo -e "\n=== Previous commit before ee420663 ==="
git show ee420663^:apps/desktop/package.json 2>/dev/null | grep '"version"' || echo "Previous commit not available"

Repository: superset-sh/superset

Length of output: 2574

---

Version downgrade detected—contradicts PR title and breaks update delivery.

The PR title states "bump version to 0.0.75" but this changes the version from 0.0.76 (on main) down to 0.0.75, which is a downgrade, not a bump. This creates critical issues:

1. Auto-update failure: Users already on 0.0.76 will not be notified of this release since electron-updater only triggers updates for higher version numbers.
2. Semantic versioning violation: Version numbers should monotonically increase.
3. Release management confusion: The version history becomes non-linear.

This suggests either the wrong branch is being merged, a merge conflict was resolved incorrectly, the release script has a bug, or an intentional rollback that requires proper documentation. The discrepancy between the commit message ("bump") and the actual change (downgrade) must be resolved before merging.

🤖 Prompt for AI Agents

In `@apps/desktop/package.json` at line 5, The package.json "version" field was
decreased to "0.0.75" which is a downgrade; update the "version" value in
apps/desktop's package.json (the "version" key) to the correct, higher semantic
version (e.g., change back to "0.0.76" or the intended new bump) so versions
monotonically increase, and then verify the release script/branch/merge
resolution that produced this change to prevent regressions; ensure the commit
message and PR title match the final "version" value before merging.