chore(desktop): bump version to 0.0.31

[Kitenite]

Bumps desktop app version to 0.0.31.

This PR was automatically created by the release script.

Summary by CodeRabbit

• Chores
  • Version update for the desktop application.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

The pull request increments the version field in apps/desktop/package.json from 0.0.30 to 0.0.31. This is a straightforward version bump with no functional, structural, or logic changes.

Changes

Cohort / File(s)	Summary
Version Bump apps/desktop/package.json	Version number incremented from 0.0.30 to 0.0.31

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~1 minute

Possibly related PRs

• chore(desktop): bump version to 0.0.30 #451: Sequential version bump in the same file, directly preceding this change (0.0.29→0.0.30 and 0.0.30→0.0.31).
• chore(desktop): bump version to 0.0.26 #414: Modifies apps/desktop/package.json to bump the desktop app version with the same pattern.
• chore(desktop): bump version to 0.0.27 #429: Updates desktop app version in apps/desktop/package.json following the same release workflow pattern.

Poem

🐰 A whisker-twitch, a version flip,
From thirty to thirty-one we skip,
No features new, just numbers grown,
Another hop up, another stone! 🎉

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	The description is minimal but covers the essential change. However, it lacks structured sections required by the template such as Related Issues, Type of Change, Testing, and Additional Notes.	Consider following the PR template more closely by adding sections for Type of Change (e.g., 'Chore') and other relevant fields, or clarify if the template is optional for automated version bump commits.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: bumping the desktop app version to 0.0.31, which is confirmed by the file summary.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch powerful-jellyfish-5e15a7

---

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

📜 Review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 8ef05b6 and 345cb69.

📒 Files selected for processing (1)

• apps/desktop/package.json (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)

• GitHub Check: Build - macOS (arm64)
• GitHub Check: Build

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Description: Verify that all release artifacts are properly updated for version 0.0.31

echo "=== Checking for CHANGELOG entries ==="
fd -t f "CHANGELOG|CHANGES|HISTORY" -x rg -l "0\.0\.31" {}

echo -e "\n=== Checking for hardcoded version references in desktop app ==="
rg -t ts -t tsx -t js -t jsx "0\.0\.30|0\.0\.31" apps/desktop/

echo -e "\n=== Checking if git tag exists for v0.0.31 ==="
git tag -l "v0.0.31" || echo "No tag found for v0.0.31"

echo -e "\n=== Checking for other package.json files that might reference desktop version ==="
fd package.json -x grep -l "version" {} 2>/dev/null | head -20

Repository: superset-sh/superset

Length of output: 721

---

🏁 Script executed:

#!/bin/bash
# Check for release scripts that might automate version bumping for desktop app
fd -t f "release|version|bump" apps/desktop/ -x grep -l "0.0.3" {} 2>/dev/null | head -10

Repository: superset-sh/superset

Length of output: 46

---

🏁 Script executed:

#!/bin/bash
# Look for release or version-related scripts
find . -type f \( -name "*release*" -o -name "*version*" \) -path "*/apps/desktop/*" -o -path "*/.github/workflows/*" | grep -E "(release|version)" | head -20

Repository: superset-sh/superset

Length of output: 136

---

🏁 Script executed:

cat -n .github/workflows/release-desktop.yml

Repository: superset-sh/superset

Length of output: 6073

---

🏁 Script executed:

cat -n apps/desktop/create-release.sh

Repository: superset-sh/superset

Length of output: 13483

---

Git tag desktop-v0.0.31 is required to trigger the release workflow.

The version increment is correctly formatted, but the release process is incomplete. The patch version follows semantic versioning correctly, however the git tag in the format desktop-v0.0.31 is missing. This tag is required to trigger the GitHub Actions release workflow that builds and publishes the desktop application.

The release script (apps/desktop/create-release.sh) automates the complete process:

1. Updates package.json version
2. Commits the change
3. Creates and pushes a git tag desktop-v${VERSION} to trigger the build workflow

Create the missing git tag and push it to trigger the release workflow:

git tag desktop-v0.0.31
git push origin desktop-v0.0.31

🤖 Prompt for AI Agents

apps/desktop/package.json lines 5-5: the package version was updated to 0.0.31
but the required git tag to trigger the release workflow is missing; create an
annotated tag named desktop-v0.0.31 on the commit that updated package.json and
push that tag to the remote (push the tag to origin) so the GitHub Actions
release workflow is triggered.

[github-actions]

🧹 Preview Cleanup Complete

The following preview resources have been cleaned up:

Service	Status
Database (Neon)	✅

Thank you for your contribution! 🎉

---

Preview resources have been processed for cleanup