Fix Fastlane metadata length violations and add CI validation - #600
Merged
Conversation
Self-contained work items (WI-1..WI-10) so agents can each pick up one issue: root cause with file:line, fixability verdict, concrete fix. Also documents unfixable-by-construction issues, philosophy declines, dedupe map, and two canned close rationales. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
nl-NL and eu-ES short_description.txt were at or over the 80-char Play Store limit; the three most recent en-US changelogs were 1.5-3x over the 500-char limit, which is what IzzySoft's F-Droid bot flagged in #276. Condensed all five to fit while keeping the same content. Also add the GitHub Action IzzySoft suggested in the thread (ashutoshgngwr/validate-fastlane-supply-metadata) to catch this class of error on PRs touching fastlane/, instead of after the fact. Fixes #276 Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
The new validate-fastlane-supply-metadata workflow (added in the
previous commit) surfaced issues the earlier manual pass missed:
- title.txt is required by the validator in every locale directory;
this repo only ever shipped it for en-US. Added it to every other
locale with the same untranslated app name ("TrackerControl"),
matching en-US.
- featureGraphic.png was 1024x512, not the required 1024x500. Cropped
6px off the top and bottom (flat background padding, no content
lost).
- The three remaining pre-2026 changelogs (751/751/841 chars) were
also over the 500-char limit; the validator checks all changelogs,
not just the current release. Condensed them, same content.
Verified against the validator's exact rules (read from its source)
with a local script: 0 errors.
Co-Authored-By: Claude Sonnet 5 <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.
Summary
nl-NLandeu-ESshort descriptions were at/over the 80-char limit; the three most recenten-USchangelogs were 1.5-3x over the 500-char limit — this is what IzzySoft's F-Droid bot was flagging in Minor errors in Fastlane structure #276. Condensed all five, same content, under the limits.ashutoshgngwr/validate-fastlane-supply-metadata), running on any PR touchingfastlane/**, so this class of error is caught before merge instead of after IzzySoft notices it in production.Closes #276
Test plan
short_description.txtis under 80 chars and every recent changelog under 500 chars via a script🤖 Generated with Claude Code