Skip to content

chore(rename): Owletto.app + Owletto.dmg companion to owletto#168#856

Merged
buremba merged 1 commit into
mainfrom
chore/rename-bundle-owletto-companion
May 18, 2026
Merged

chore(rename): Owletto.app + Owletto.dmg companion to owletto#168#856
buremba merged 1 commit into
mainfrom
chore/rename-bundle-owletto-companion

Conversation

@buremba
Copy link
Copy Markdown
Member

@buremba buremba commented May 18, 2026

Summary

Companion to owletto#168 (bundle renamed Lobu.app → Owletto.app). Three coordinated deltas:

File Change
`.github/workflows/mac-release.yml` archive path → `Owletto.app`, DMG volume name + filename → `Owletto` / `Owletto.dmg` (build, codesign, notarize, staple, release asset, Sparkle appcast `--dmg-url`). `Lobu.xcarchive` (runner temp dir) and `lobu-v` tag prefix stay.
`packages/landing/src/components/HeroProductCard.tsx` Download .dmg button URL → `Owletto.dmg`.
`packages/owletto` submodule pointer → `a682edc` (merged owletto#168).

Why

macOS Privacy & Security panels (Full Disk Access, Notifications, etc.) key off the `.app` bundle filename. Earlier `EXECUTABLE_NAME = Owletto` rename fixed Activity Monitor / `ps` but FDA still shows "Lobu.app". The bundle rename in owletto#168 produces `Owletto.app` — this PR wires the rest of the publishing pipeline to ship + link it correctly.

Migration for existing users

Sparkle's in-place updater overwrites bundle contents but keeps the existing folder name. Anyone on `/Applications/Lobu.app` will continue to show "Lobu.app" in Finder + FDA until they manually replace the install. Worth a line in the next release's release notes.

Test plan

  • mac-release.yml: scheme check + bundle-name check still pass (only path strings changed; scheme = Lobu, CFBundleName/Display = Owletto unchanged).
  • Landing page: `bun run build` in packages/landing succeeds.
  • CI: lint + typecheck pass with the bumped submodule.
  • Next mac-release: produces `Owletto.dmg` attached to the release; landing page Download .dmg button resolves; existing installs auto-update via Sparkle to a bundle whose contents now say Owletto.

Summary by CodeRabbit

  • Chores
    • Streamlined the macOS application release workflow to improve build efficiency, code signing, notarization, and application distribution processes
    • Updated macOS application download links throughout the platform to ensure users are directed to the correct release packages
    • Updated internal development dependencies and project submodules to the latest compatible versions

Review Change Stack

Coordinated companion to the bundle rename in owletto#168
(merged as a682edc). Three deltas:

- mac-release.yml: archive path Lobu.xcarchive/Products/Applications/Lobu.app
  → Owletto.app, DMG --volname / --icon → Owletto, DMG output filename
  Lobu.dmg → Owletto.dmg (everywhere: build, codesign, notarize, staple,
  release asset, Sparkle appcast --dmg-url). Lobu.xcarchive (just a
  runner temp dir) and 'lobu-v<version>' tag prefix stay — release
  naming convention is unchanged.

- packages/landing: HeroProductCard download link Lobu.dmg → Owletto.dmg
  so the public Download .dmg button resolves once the next release
  publishes.

- packages/owletto: submodule pointer 74f441f → a682edc.

Migration for existing users on /Applications/Lobu.app: Sparkle's
in-place updater overwrites bundle contents but keeps the original
folder name. Old installs continue to show 'Lobu.app' in Finder + FDA
until manually replaced. Will note in the next release's release notes.
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 18, 2026

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 49d8c4d4-1efb-466c-ad82-943f4de77d10

📥 Commits

Reviewing files that changed from the base of the PR and between 741a4d7 and 7ac60e9.

📒 Files selected for processing (3)
  • .github/workflows/mac-release.yml
  • packages/landing/src/components/HeroProductCard.tsx
  • packages/owletto

📝 Walkthrough

Walkthrough

The PR migrates the macOS release workflow and landing page download references from the Lobu product to Owletto. The release workflow now builds and signs Owletto.app, produces Owletto.dmg, notarizes/staples that DMG, and uploads it to the release. Landing page download links and Sparkle appcast URLs are updated to point to the new artifact.

Changes

Owletto macOS Release Migration

Layer / File(s) Summary
macOS release workflow build, sign, and publish
.github/workflows/mac-release.yml
Workflow header comments are updated to reference Owletto. Core build/sign/notarization steps operate on Owletto.app and output Owletto.dmg. Appcast publishing and DMG variable references are updated to use the new Owletto artifact paths. Release tag remains lobu-v<version>.
Landing page macOS download link
packages/landing/src/components/HeroProductCard.tsx
macOS device download action is updated to point to Owletto.dmg in the GitHub Release instead of Lobu.dmg.
Owletto submodule version bump
packages/owletto
Submodule pointer is advanced to a new commit.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

  • lobu-ai/lobu#840: Updates the packages/owletto submodule pointer in a related commit bump.
  • lobu-ai/lobu#825: Also updates the packages/owletto git submodule pointer to a pinned version.

Poem

🐰 From Lobu's dmg to Owletto's new flight,
The workflows now build and sign with all their might,
Release pipelines shift, appcast URLs gleam,
A migration smooth—one cohesive team! ✨

✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/rename-bundle-owletto-companion

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

ESLint skipped: no ESLint configuration detected in root package.json. To enable, add eslint to devDependencies.


Comment @coderabbitai help to get the list of available commands and usage tips.

@buremba buremba merged commit f19af3c into main May 18, 2026
18 of 19 checks passed
@buremba buremba deleted the chore/rename-bundle-owletto-companion branch May 18, 2026 03:19
@codecov-commenter
Copy link
Copy Markdown

⚠️ Please install the 'codecov app svg image' to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

buremba added a commit that referenced this pull request May 18, 2026
release-please doesn't auto-bump submodules between its PR
opening and merge. Main has moved past the release branch's
pinned owletto SHA (74f441f) by three commits (#856 bundle
rename, #857 goal-row-Terminal, #858 SyncDispatcher refactor).
Without this bump the v7.1.0 release would ship lobu pointing
at an owletto that doesn't have the work the changelog
describes, and the Submodule Drift check stays red.
buremba added a commit that referenced this pull request May 18, 2026
* chore(main): release lobu 7.1.0

* chore(submodule): bump owletto to b9c3258 for release v7.1.0

release-please doesn't auto-bump submodules between its PR
opening and merge. Main has moved past the release branch's
pinned owletto SHA (74f441f) by three commits (#856 bundle
rename, #857 goal-row-Terminal, #858 SyncDispatcher refactor).
Without this bump the v7.1.0 release would ship lobu pointing
at an owletto that doesn't have the work the changelog
describes, and the Submodule Drift check stays red.
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.

2 participants