chore: switch to release-please + fix broken release workflow#22
Merged
StuBehan merged 1 commit intoApr 30, 2026
Merged
Conversation
The existing release.yml referenced notifier/*.swift which were deleted in the single-binary refactor, and auto-tag.yml read CFBundleShortVersionString from notifier/Info.plist (now panel/Info.plist). Both have been silently broken since refactor/single-binary merged. This commit replaces them with a release-please-driven flow: - release-please.yml watches conventional commits on main, opens a Release PR that bumps .release-please-manifest.json + regenerates CHANGELOG.md. Merging that PR creates the tag and GitHub Release. - release.yml triggers on the tag, builds arm64 + x86_64 sequentially via build.sh's existing -target flag, lipos into a universal binary, re-signs (lipo invalidates the per-arch ad-hoc sigs), stamps the version from the tag into Info.plist, and packages a self-contained tarball. - The tarball includes the prebuilt bundle plus notify.sh / phrases / install.sh / uninstall.sh / notify.conf.example so users who download a release don't need swiftc. - install.sh now skips the swiftc rebuild when build/stack-nudge.app is already present, so the release-tarball install path runs in seconds instead of building from source on the user's machine. - auto-tag.yml is removed; release-please handles tagging now. Bootstrap manifest version is 1.1.2 to match the latest tag and the current Info.plist. End-to-end verified locally: tarball extracts, prebuilt-detection finds the bundle, the resulting mach-o is a valid arm64 executable, and shellcheck still passes on the extracted install.sh. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
1 participant
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.
The existing release.yml referenced notifier/*.swift which were deleted in the single-binary refactor, and auto-tag.yml read CFBundleShortVersionString from notifier/Info.plist (now panel/Info.plist). Both have been silently broken since refactor/single-binary merged.
This commit replaces them with a release-please-driven flow:
Bootstrap manifest version is 1.1.2 to match the latest tag and the current Info.plist.
End-to-end verified locally: tarball extracts, prebuilt-detection finds the bundle, the resulting mach-o is a valid arm64 executable, and shellcheck still passes on the extracted install.sh.
Summary
Changes
Testing
Related issues