Repository navigation
Add release automation with generated changelogs and dry run - #18
Merged
Merged
Conversation
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
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.
Adds a manually requested release flow that generates EN/RU changelogs, opens a release PR, requires full CI, then squash-merges and tags the verified merged commit. GitHub Releases use the same changelog files as F-Droid.
Includes a read-only dry run, setup/recovery instructions, and Samsung Auto Blocker installation guidance in both languages. This PR does not bump the app version or publish a release.
Validation: Fastlane Python checks (3 server tests and 8 release tests), formatting, workflow YAML/shell syntax, and Ruby syntax passed. The release tests cover dry-run non-mutation, CI gates, merge and tag retries with a local Git repository and mocked APIs; live credentials have not yet been exercised.