Release fork updates on demand with independent version numbers - #10
Merged
Merged
Conversation
EricRasputin
changed the title
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.
Merges to main now run CI without packaging or publishing an app update. To ship a batch of changes, manually run CI on main and enable Publish fork update after checks pass (main only); the option is off by default.
Fork versions are independent of upstream and CI run numbers. The next release starts at 1.0.0 (upgrading from the existing 0.2.12), then defaults to the next published fork patch version. An optional version input supports deliberate minor or major releases. Tags retain the fork-v prefix, and the existing app identity, updater key, and feed remain in place.
Version selection runs inside the serialized release workflow. It ignores upstream releases, skips an already-released commit, rejects older snapshots and duplicate/older explicit versions, and preserves drafts belonging to other commits. Both macOS packages must still pass all checks and finish before publication. Bundled notes include the commits since the preceding fork release, with the upstream version retained as provenance.
Validation: actionlint and git diff --check pass; all 13 release tests pass, including real-git tests for version selection, draft retries, stale commits, and batched notes. A read-only check against live release metadata selects 1.0.0. CI checks run on macOS, Linux, and Windows. This PR does not publish a new app release.