Add Ubuntu deb release artifact

[Abhishek-Gawade-programmer]

What Changed

• added a dist:desktop:deb script for building a Linux .deb artifact
• updated the release workflow to build and publish an Ubuntu .deb alongside the existing Linux AppImage artifact
• updated the release docs to mention the .deb artifact and clarify that Linux auto-update remains AppImage-only

Why

Ubuntu users currently only get the AppImage artifact from the desktop release pipeline.

This keeps the existing AppImage path intact for Linux auto-update behavior, while also publishing a native .deb package for
direct Ubuntu installation. That keeps the change small and avoids changing the current updater assumptions.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes
• I included a video for animation/interaction changes

---

Note

Medium Risk
Modifies the release CI matrix and asset publishing steps; mistakes could break or delay desktop releases, but changes are additive and scoped to packaging/publishing.

Overview
Adds an Ubuntu x64 .deb to the desktop release pipeline alongside the existing Linux AppImage.

The GitHub Actions release.yml build matrix now runs a Linux deb target and the workflow copies/uploads *.deb assets into the GitHub Release. A new dist:desktop:deb script is added for local builds, and release docs are updated to note the new artifact and that Linux auto-update remains AppImage-based.

^{Reviewed by Cursor Bugbot for commit 009af84. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Add Ubuntu x64 .deb artifact to the release build and publish pipeline

• Adds a Linux Ubuntu x64 .deb target to the build matrix in release.yml, and includes *.deb files in both the file-copy and GitHub release upload steps.
• Adds a dist:desktop:deb npm script in package.json for local .deb builds.
• Updates docs/release.md to note that five artifacts are now built, and clarifies that the .deb is for direct installation while AppImage targets auto-update.

^{Macroscope summarized 009af84.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 293a6421-e8c1-48fd-bf88-fca2993beadc

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

Tip

💬 Introducing Slack Agent: The best way for teams to turn conversations into code.

Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.

• Generate code and open pull requests
• Plan features and break down work
• Investigate incidents and troubleshoot customer tickets together
• Automate recurring tasks and respond to alerts with triggers
• Summarize progress and report instantly

Built for teams:

• Shared memory across your entire org—no repeating context
• Per-thread sandboxes to safely plan and execute work
• Governance built-in—scoped access, auditability, and budget controls

One agent for your entire SDLC. Right inside Slack.

👉 Get started

---

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

[cursor]

Duplicate artifact name causes release workflow failure

High Severity

The new Ubuntu .deb x64 matrix entry has platform: linux and arch: x64, identical to the existing Linux x64 (AppImage) entry. The artifact upload step on line 357 derives its name from desktop-${{ matrix.platform }}-${{ matrix.arch }}, so both jobs produce desktop-linux-x64. With actions/upload-artifact@v7, the second job to finish will fail because an artifact with that name already exists and no overwrite: true is set. The artifact name needs to incorporate the target to differentiate the two Linux builds.

Additional Locations (1)

• .github/workflows/release.yml#L354-L358

 

^{Reviewed by Cursor Bugbot for commit fbd1741. Configure here.}

[macroscopeapp]

Approvability

Verdict: Needs human review

CI/CD changes to add Ubuntu .deb release artifact. An unresolved high-severity review comment identifies that the new matrix entry would create duplicate artifact names with the existing Linux AppImage build, causing workflow failures. This bug should be addressed before merging.

^{You can customize Macroscope's approvability policy. Learn more.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

There are 2 total unresolved issues (including 1 from previous review).

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 009af84. Configure here.}

[cursor]

Linux updater metadata collision between AppImage and deb builds

Medium Severity

Both the AppImage and deb builds will generate identically-named auto-update metadata files (latest-linux.yml or nightly-linux.yml) because resolveGitHubPublishConfig injects a publish config for all targets. When artifacts are merged via download-artifact with merge-multiple: true, one metadata file silently overwrites the other. If the deb metadata wins, AppImage auto-update users get pointed to a .deb file, breaking auto-updates. The macOS builds handle a similar multi-arch collision via manifest renaming (lines 335–340), but no equivalent handling exists for the two Linux targets.

Additional Locations (1)

• .github/workflows/release.yml#L328-L329

 

^{Reviewed by Cursor Bugbot for commit 009af84. Configure here.}