docs(fastlane): add F-Droid changelogs for 1.2.0 (102000) - #58
Merged
Merged
Conversation
The v1.2.0 tag build failed in the "Verify release metadata matches tag" step because the per-release changelog files for versionCode 102000 were missing in both locales. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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
v1.2.0tag build (run 32894643357) failed in the Verify release metadata matches tag step:app/version.propertieswas already bumped correctly in #57 — only the per-release changelogs were missing. This adds them for both locales, worded from the v1.2.0 release notes (widget #50, accessibility screen lock #52, Quick Settings tile #51).After merge the
v1.2.0tag has to be moved to the newmainhead and re-pushed so the release build reruns.🤖 Generated with Claude Code