|
| 1 | +--- |
| 2 | +name: update-store-release-notes |
| 3 | +description: Update and localize FeedFlow release notes when the user provides platform-specific changelog copy. Use for Android Google Play, iOS App Store, macOS App Store, and Windows Microsoft Store release-note updates, including requests to translate notes for every configured store locale. |
| 4 | +--- |
| 5 | + |
| 6 | +# Update FeedFlow Store Release Notes |
| 7 | + |
| 8 | +Use the user-provided copy as the source of truth. Preserve platform-specific wording; do not force one platform's copy onto another. |
| 9 | + |
| 10 | +## Workflow |
| 11 | + |
| 12 | +1. Inspect the target artifacts, locale set, and current working-tree status before editing. |
| 13 | +2. Replace the English source and translate it for every configured target locale. Do not invent feature claims or omit user-supplied bullets. |
| 14 | +3. Keep the writing short, user-facing, and benefit-led. Preserve bullet formatting when supplied. |
| 15 | +4. Validate the exact artifact format and limits. Run `git diff --check`. Run the smallest relevant build or validation only when the changed artifact requires it. |
| 16 | + |
| 17 | +Respect a user request to translate store copy even if general project localization guidance normally delegates translations. |
| 18 | + |
| 19 | +## Android: Google Play |
| 20 | + |
| 21 | +- Write production notes to `androidApp/src/googlePlay/play/release-notes/<locale>/production.txt`. |
| 22 | +- `en-US/production.txt` is the English source. Every existing locale directory is a target; create `production.txt` in empty locale directories. |
| 23 | +- Keep each note at or below 500 characters: `wc -m androidApp/src/googlePlay/play/release-notes/*/production.txt`. |
| 24 | +- Do not edit `alpha.txt` unless the user explicitly requests alpha-track notes. |
| 25 | + |
| 26 | +## iOS and macOS: App Store Connect |
| 27 | + |
| 28 | +- Treat iOS and macOS as separate products: accept and maintain separate platform copy. |
| 29 | +- Inspect App Store Connect first to discover the version and its actual localization set. Use `asc` to pull the relevant version localizations, update each locale's `whatsNew`, then pull/validate again to confirm the remote result. |
| 30 | +- Use `en-US` as the source locale and translate only into locales exposed for that specific product/version. Do not create an App Store task for a locale App Store Connect does not support. |
| 31 | +- Use the platform's field limits reported by `asc`; shorten translations as needed while retaining all material points. |
| 32 | +- Never upload or submit a build as part of a text-only release-note request unless the user explicitly asks. |
| 33 | + |
| 34 | +## Windows: Microsoft Store |
| 35 | + |
| 36 | +- Update `assets/storecopy/microsoft-store-release-notes.json`. |
| 37 | +- Keep the top-level `notes` object. Each locale value is an array of non-empty bullet strings; the Store publishing script joins the array with newlines. |
| 38 | +- Match every Partner Center listing locale. The publisher validates missing locales case-insensitively and warns about unused ones. Discover the live set when credentials are available rather than assuming a static list. |
| 39 | +- The publishing workflow passes this file to `.github/scripts/publish-msix-to-store.ps1`; validate the JSON before handoff, for example with `jq empty assets/storecopy/microsoft-store-release-notes.json`. |
| 40 | +- Do not publish or commit the Microsoft Store submission unless the user explicitly asks; editing the local release-note file is sufficient. |
| 41 | + |
| 42 | +## Final Report |
| 43 | + |
| 44 | +State the platforms and locale count updated, list any unavailable or unsupported locales, and report the validations actually run. |
0 commit comments