Repository navigation
chore(desktop): show the app as buzz - #1522
Conversation
set productName and window titles to buzz so the macos bundle, menu bar and dock show buzz instead of buzz foundation. the bundle identifier is unchanged, so app data, webview storage and keychain items stay put. windows and linux keep productName "buzz foundation": nsis keys its install dir and uninstall registry entries on it, and the deb package name is derived from it, so renaming there would install side by side or conflict with the existing buzz-foundation package on update. release.yml now looks for Buzz.app in the dmg and updater archive. the macos updater strips the archive top-level dir, so existing installs update in place under their current file name.
wesbillman
left a comment
wesbillman
left a comment
There was a problem hiding this comment.
🤖 Star Lord’s automated source review via Wes’s account, integrating independent Rocket (packaging/lifecycle), Mantis (correctness/security), and Groot (product/accessibility) reviews.
One P2 finding inline: preserve the documented manual promotion/recovery path for pre-rename preview archives. Source assessment: 8/10 until that compatibility gap is repaired. The intended macOS rename, stable identifier/binary, and Windows/Linux package-name continuity are otherwise coherent in the inspected source.
Reviewed head: ef50b70. Base/merge-base: f941667. All six changed files, release producer/consumer paths, relevant identity/release docs and upstream updater 2.13.3 implementation were inspected. The updater strips the archive root and targets the running bundle, consistent with the disclosed in-place naming behavior. Fresh-install replacement of legacy Buzz is explicitly disclosed in the PR. No disclosure issue found in the public PR description or changed content; no attached images were present.
Validation: source only; no tests, builds, installers, apps or release workflows executed. No browser journeys added or removed. A hosted CI snapshot showed CI required failing through WebKit shard 2/12; other executed checks passed, with Windows native validation and flake lanes skipped. The failure’s cause was not investigated or attributed to this diff. Signed packaging, old-to-new install/relaunch, Finder/Dock/menu appearance, native consent and error/retry focus, and human acceptance remain unverified. This COMMENT is advisory, not approval or merge authorization.
| [[ -s "$RUNNER_TEMP/candidate/$asset" && -s "$RUNNER_TEMP/candidate/$asset.sig" ]] | ||
| done | ||
| tar -xOzf "$RUNNER_TEMP/candidate/$archive" 'Buzz Foundation.app/Contents/MacOS/buzz-foundation' > "$RUNNER_TEMP/candidate/buzz-foundation" | ||
| tar -xOzf "$RUNNER_TEMP/candidate/$archive" 'Buzz.app/Contents/MacOS/buzz-foundation' > "$RUNNER_TEMP/candidate/buzz-foundation" |
There was a problem hiding this comment.
🤖 [P2] Keep existing preview archives promotable after the rename
promote_version intentionally skips rebuilding and downloads an existing release. The base workflow packages Buzz Foundation.app (base lines 145–152), but this extraction now accepts only Buzz.app. Therefore a manual recovery using an otherwise eligible pre-rename candidate, or a same-version repromotion of a pre-rename feed, exits at tar under set -e before the verification/feed steps. Those operations are explicitly supported by docs/releases.md:67–72 and the same-version branch in scripts/preview-feed.mjs.
Accept both known bundle-root names when locating the candidate’s Contents/MacOS/buzz-foundation, while keeping the signature, embedded-key/endpoint and version checks. Cover extraction for both old and new archive layouts; new builds should continue producing Buzz.app.
Main renamed the macOS product to "Buzz" (#1522) but kept the executable `buzz-foundation`. `tauri dev` runs that bare executable with no .app bundle, so LaunchServices names the process after the executable filename, and muda's default About/Hide/Quit items read `NSRunningApplication.localizedName`, which is that same filename. Neither the embedded Info.plist nor `productName` influences either, so the Dock and application menu of a development build still read "buzz-foundation". Rename the Cargo package to `Buzz` so the binary itself carries the display name; the lib target stays `buzz_foundation_lib`. This is the package-rename variant already proven with the Tauri CLI in Staged. Follow the new name everywhere the binary or package is spelled out: CI package selectors, release verification (`Buzz.app/Contents/MacOS/Buzz`, `Buzz.exe`, `usr/bin/Buzz`), the AppImage shim and its test, deny.toml dependency-path comments, and docs. Unchanged on purpose: the `dev.local.buzz.foundation` identifier, the `Buzz Foundation` productName main pins for Linux/Windows installers (and the `usr/lib/Buzz Foundation/` paths it drives), `~/.buzz-foundation*` directories, and the npm package name. Co-Authored-By: Claude Fable 5.1 <[email protected]> Signed-off-by: Matt Toohey <[email protected]>
Renames the app as users see it on macOS from Buzz Foundation to Buzz. No data or identity migration.
Changes
tauri.conf.json:productNameand window title →Buzz. This drivesBuzz.app,CFBundleName(menu bar), and the Dock/Finder name for fresh installs.tauri.linux.conf.json/tauri.windows.conf.json: window title →Buzz;productNamepinned toBuzz Foundation.release.yml: DMG / updater-archive pathsBuzz Foundation.app→Buzz.app.index.html<title>,docs/deep-links.mdbundle path.Unchanged on purpose
identifierstaysdev.local.buzz.foundation: app data, WebKit storage, Keychain access and notification permissions are untouched.buzz-foundation;~/.buzz-foundation/...paths unchanged.productName: NSIS keys its install dir and uninstall registry entry on it (rename → side-by-side install), and the debPackage:is its kebab-case (rename → a newbuzzpackage that conflicts with the installedbuzz-foundationover/usr/bin/buzz-foundation). Deferred to the identity migration.Existing macOS preview installs
The updater strips the archive's top-level directory and installs into the current app path, so updates still land in place. The file stays
Buzz Foundation.app, so Finder/Dock keep that name until a fresh DMG install; the menu bar showsBuzz.Fresh DMG installs are
/Applications/Buzz.app, the same file name as 0.X: dragging it in prompts to replace the 0.X app (0.X data is kept).