Restored .deb and .rpm packaging targets missed out from Tauri -> Electron migration#2087
Open
harshit110927 wants to merge 2 commits into
Open
Restored .deb and .rpm packaging targets missed out from Tauri -> Electron migration#2087harshit110927 wants to merge 2 commits into
harshit110927 wants to merge 2 commits into
Conversation
…electron-builder.yml Add Linux desktop metadata and deb/rpm targets to electron-builder.yml
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
|
@harshit110927 is attempting to deploy a commit to the Different AI Team on Vercel. A member of the Team first needs to authorize it. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Restored .deb and .rpm Linux packaging targets that were present in the
Tauri build but not carried over when electron-builder.yml was written
for the Electron migration. Also added a linux.desktop metadata block
so both formats register correctly in system app launchers after install.
Why
v0.11.207 shipped openwork-desktop-linux-amd64.deb and
openwork-desktop-linux-aarch64.rpm as release artifacts. The Electron
migration dropped both. Ubuntu/Debian and Fedora/RHEL users currently
have no native package format available and no system launcher entry
after installing the app. This restores what was there before.
Issue
Closes #2084
Scope
apps/desktop/electron-builder.yml, linux block only.
Added deb and rpm to linux.target alongside the existing AppImage and
tar.gz entries.
Added linux.desktop block with Name, Comment, Categories, and
StartupWMClass so installed packages register in system app launchers
under the Development category.
Out of scope
Windows and macOS packaging blocks are untouched. AUR packaging is a
separate workflow and is not affected. Snap and Flatpak targets are not
included. Updater feed configuration for the new formats is not handled
here and can follow separately if needed.
Testing
Ran
block was modified and no other sections were touched
YAML config change with no TypeScript involved
Result
CI status
change and the new targets build independently from existing ones
Manual verification
release assets for amd64
app launcher under the Development category with the correct name
Evidence
Prior Tauri release confirming these formats were already shipped to
users before the migration:
https://github.com/different-ai/openwork/releases/tag/v0.11.207
No UI changes so no screenshot is applicable.
Risk
Low. Two new build targets are added alongside AppImage and tar.gz which
remain unchanged. If deb or rpm builds fail in CI they fail independently
and do not affect the existing AppImage or tar.gz outputs.
Rollback
Remove deb and rpm from linux.target and remove the linux.desktop block
in apps/desktop/electron-builder.yml. Each is a straightforward line
deletion with no downstream effects.