Skip to content

Rename snap to lemonade-desktop#19

Merged
kenvandine merged 1 commit intostablefrom
lemonade-desktop-stable
Apr 14, 2026
Merged

Rename snap to lemonade-desktop#19
kenvandine merged 1 commit intostablefrom
lemonade-desktop-stable

Conversation

@kenvandine
Copy link
Copy Markdown
Member

@kenvandine kenvandine commented Apr 14, 2026

Summary

  • Renames the snap from lemonade to lemonade-desktop (name, adopt-info, part, app, desktop file)
  • Adds a pseudo content slot (lemonade-desktop, content: lemonade-desktop) mirroring the pattern used by lemonade-server, so the transitional lemonade snap can express a runtime dependency on this snap via the content interface and snapd will auto-install it
  • Retains source-tag: v10.2.0 for stable/candidate channel builds
  • No changes to snap-publish.yaml — it already publishes whatever snap is built, so it will naturally publish lemonade-desktop to candidate

Test plan

  • Build the snap and verify the snap name is lemonade-desktop
  • Verify snap connections lemonade shows lemonade:lemonade-desktop lemonade-desktop:lemonade-desktop after installing both snaps
  • Verify the app launches correctly as lemonade-desktop
  • Verify lemonade-server is still auto-installed via the existing content plug
  • Verify push to stable triggers publish to candidate channel

🤖 Generated with Claude Code

- Rename snap name, adopt-info, part, app, and desktop file from
  lemonade to lemonade-desktop
- Add pseudo content slot (content: lemonade-desktop) mirroring the
  pattern used by lemonade-server, so the transitional lemonade snap
  auto-installs this one via the content interface
- Retain source-tag: v10.2.0 for stable/candidate channel builds

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@kenvandine kenvandine merged commit 71ea39e into stable Apr 14, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant