Skip to content

feat(release): render and upload the store screenshots - #8

Merged
ThePhaseless merged 1 commit into
mainfrom
feat/store-screenshots
Oct 6, 2026
Merged

ThePhaseless merged 1 commit into
mainfrom
feat/store-screenshots

Conversation

@ThePhaseless

Copy link
Copy Markdown
Contributor

Summary

  • flutter-screenshots.yml (reusable): runs the app's <task>:android mise task on Linux (with Noto Color Emoji, as on Android phones) and <task>:ios on macOS (with the system San Francisco and emoji fonts); uploads screenshots-android and screenshots-ios.
  • flutter-release.yml: new screenshots-task input. Production releases and promotions render the screenshots from the tag, and the store jobs replace the ones that differ:
    • google_play.py: every listing language (en-US, else en) gets its folder for phone, tablet-7 and tablet-10, compared by SHA-256, in the edit that releases the version. Testing tracks keep the listing.
    • app_store_submit.py: every App Store version localization gets its folder for iphone-6.9 (APP_IPHONE_67, the required large size) and ipad-13 (APP_IPAD_PRO_3GEN_129), compared by MD5; uploads through Apple's upload operations and waits for processing before App Review.
  • Tests: mocks for the listing images and screenshot sets; the App Store Connect operations added to the trimmed spec verbatim; DELETE in the mock server.

Test plan

  • python3 -m unittest discover -s tests: 42 passed
  • mise run lint: actionlint, zizmor, Terraform and Markdown clean

🤖 Generated with Claude Code

flutter-screenshots.yml runs the app's <task>:android (Linux, Noto Color
Emoji) and <task>:ios (macOS, San Francisco) mise tasks. With the new
screenshots-task input, production releases replace the Google Play
listing and App Store version screenshots that differ, per language.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@ThePhaseless
ThePhaseless merged commit 86a492a into main Oct 6, 2026
3 checks passed
@ThePhaseless
ThePhaseless deleted the feat/store-screenshots branch October 6, 2026 13:17
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