Show fork versions with their pinned upstream release - #11
Merged
Merged
Conversation
EricRasputin
marked this pull request as ready for review
September 14, 2026 17:08
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 app previously showed only the fork version, making it hard to tell which upstream release it included. Settings and the native About window now show a paired version such as 1.0.0 (0.1.46), with an explicit upstream label. The updater continues to use the plain fork version.
Record the upstream repository, tag, version, and exact commit in
upstream-release.jsonand bundle it into the app. Packaging checks that the source version matches the record, the tag points to the recorded commit, and the build contains that commit. Both architecture packages must report matching provenance. Release titles use the paired display, and update manifests include the upstream record.The record changes when an upstream release is incorporated; it never follows the latest upstream version dynamically. Fork numbering and manual release controls remain independent.
Validation: 41 targeted frontend/updater tests and all 15 release tests pass; TypeScript, workflow validation, and diff checks pass. An isolated macOS release build succeeds and its code signature verifies. The native About window and Settings both report 1.0.0 (0.1.46), while Info.plist retains the plain app version 1.0.0. The test app has been closed. This PR does not publish or install an app release.