Skip to content

Preserve release history with verified merge commits - #81

Merged
andre487 merged 1 commit into
mainfrom
fix/release-merge-commit
Oct 11, 2026
Merged

andre487 merged 1 commit into
mainfrom
fix/release-merge-commit

Conversation

@andre487

@andre487 andre487 commented Oct 11, 2026 •

Copy link
Copy Markdown
Owner

Release automation currently squash merges its generated PR. Use a normal merge commit so the release branch history remains reachable, then tag that actual merge commit after full CI.

The finalizer requests GitHub merge_method=merge and verifies that the resulting commit has exactly the tested base and PR head as its two parents, as well as the tested tree. A manually squash-merged or fast-forwarded release is rejected before tagging. Existing branch-protection and unchanged-main checks remain in place.

Update the real-Git integration test to create a merge commit and assert its parents, including rejection of a one-parent commit. Synchronize EN/RU release and Fastlane documentation and record the release decision in AGENTS.md.

Validation: bundle exec fastlane android python_checks passes all 61 tests, pinned Black and isort checks. No release was created and existing tags were left unchanged.

APK artifacts

Built from commit 8b00521f by CI run #293.
Artifacts expire after 14 days. Neither APK uses the MegaProxy release key.

@andre487
andre487 enabled auto-merge (squash) October 11, 2026 11:48
@andre487
andre487 merged commit 3f48cc3 into main Oct 11, 2026
16 checks passed
@andre487
andre487 deleted the fix/release-merge-commit branch October 11, 2026 11:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant