The swiss army knife of lossless video/audio editing
Document how to write store release notes
Claude960f65d0c78e
diff --git a/AGENTS.md b/AGENTS.mdindex b11772a8..34d5d748 100644--- a/AGENTS.md+++ b/AGENTS.md@@ -17,3 +17,11 @@ When preparing a release, run `yarn release-notes` to collect these since the la## FFmpegOnly the bundled FFmpeg version (`script/downloadFfmpeg.ts`) is supported. Don't add or keep code for compatibility with older FFmpeg versions (e.g. old option names or log formats). When upgrading FFmpeg, remove such code.++## Store release notes++The stores lag behind GitHub releases, so their "What's new" text must cover every version since the one currently live in that store. Ask which version that is (Mac App Store: App Store Connect; Microsoft Store: Partner Center → the product's current submission → Packages), then combine `versions/*.md` after it up to the version being released.++- Plain text, no Markdown, code formatting, issue references or links. Use plain-language feature names instead of internal action/variable names.+- Leave out what doesn't apply to that store's build: items for other platforms (App Review rejects mentions of other platforms), GitHub-only builds, custom FFmpeg path (not in the Mac App Store build), update checks.+- Microsoft Store: max 1500 characters. Mac App Store: max 4000 characters.diff --git a/CONTRIBUTING.md b/CONTRIBUTING.mdindex 92b31841..fd69fe88 100644--- a/CONTRIBUTING.md+++ b/CONTRIBUTING.md@@ -129,7 +129,7 @@ Usually some time after the GitHub release, once no serious regressions have bee3. "Packages": click the caret next to "Unchanged", then drag-drop both renamed files into the upload area. Both architectures go in the same submission and the Store serves the right one to each device (if a submission ever used an `.appxbundle`, later ones must too, see [#2789](https://github.com/mifi/lossless-cut/issues/2789))4. Tick "Roll out update gradually", start rollout with 0%, wait for the uploads to finish and click "Save"5. "Submission Options" (caret): tick "Don't publish this submission until I select Publish now"-6. "Store listings" → "Languages supported in packages" → "English (United States)": replace "What's new in this version". If needed, also update "Description", "Product features" and screenshots+6. "Store listings" → "Languages supported in packages" → "English (United States)": replace "What's new in this version" (see [Store release notes](./AGENTS.md#store-release-notes)). If needed, also update "Description", "Product features" and screenshots7. Go back and click "Submit for certification"8. Once certified, publish it, and increase the rollout by ~15% every day or so@@ -139,7 +139,7 @@ Tag builds already upload the build to App Store Connect (`(MacOS) Upload to Mac1. In [App Store Connect](https://appstoreconnect.apple.com/apps/1505323402/distribution), create a new version2. "Build": click "Add Build" and pick the build of this version-3. Update "What's New in This Version". If needed, also update "Description" and screenshots+3. Update "What's New in This Version" (see [Store release notes](./AGENTS.md#store-release-notes)). If needed, also update "Description" and screenshots4. "App Store Version Release": tick "Manually release this version"5. "Phased Release for App Store Automatic Updates": tick "Release update over 7-day period using phased release"6. Save, then "Add for Review"