Document the release process - #11
Merged
Merged
Conversation
Documents how a signed release is actually cut, adapted from trsdn/OpenSwitchr's RELEASE_CHECKLIST.md for what's genuinely different here: the version comes from the git tag automatically (build-app.sh and the broker's assemble_openpromptr both derive it), so there's no manual Info.plist bump step; there's no diag CLI, so verification is the README's runtime self-test or a manual pass over each source type; and there's a dedicated section on testing the updater itself, which needs a second release to have anything to find. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01XBbvDgF84mTXMJMcioTX4U
4 tasks
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.
Summary
Third of issue #7's four checklist items: documents how a release is actually cut, now that the broker profile (trsdn/macos-notarization-broker#49) and AppUpdater integration (#10) are both merged.
Adapted from
trsdn/OpenSwitchr'sRELEASE_CHECKLIST.md, the closest existing precedent, but corrected for what's genuinely different in this repo:Info.plist's version. OpenPromptr doesn't need that:build-app.shand the broker'sassemble_openpromptrboth derive the version from the git tag automatically (this session's earlier work). The checklist calls this out explicitly so nobody "fixes" a version mismatch by hand-editing the plist.openswitchr-diag; OpenPromptr has nothing equivalent, so verification is the README's existing runtime self-test, or a manual pass over each source type.Links added from
AGENTS.mdand the README's "Checking for updates" section.Remaining after this: actually cutting the first release and testing an update with the second (issue #7's last item) — needs real Apple Developer credentials and manual broker invocation, so left to the maintainer's own timing.
Test plan
swift build,swift format lint --strictclean (docs-only change; sanity-checked nothing else broke)#optional-runtime-self-test,#upgrading-from-teleprompter-mirror)🤖 Generated with Claude Code
https://claude.ai/code/session_01XBbvDgF84mTXMJMcioTX4U