Repository navigation
docs: share store release-note checks - #294
piotr-iohk wants to merge 1 commit into
Conversation
talosmachina
left a comment
There was a problem hiding this comment.
No findings. Adds the shared store release-note method (docs/store-release-notes.md) and links it from AGENTS.md and the README, for the native /release commands to load. Reviewed 8c195a3, light tier (docs only, nothing to build).
What I checked, and 3 candidates I ruled out
Read in full: docs/store-release-notes.md, the AGENTS.md and README.md hunks, and both consumers (synonymdev/bitkit-android#1791, synonymdev/bitkit-ios#1224)
CI: no checks run on this branch
Ruled out
- Language list drifting from the consumers: the guide's English, French, Spanish, Portuguese and German match the five headings both
/releasecommands write to.ai/release-notes-{version}.md. - Check record committed by accident:
.ai/store-notes-check-{version}.mdsits under.ai/, which both app repos'.gitignorealready excludes. - Policy statements: guideline 2.3.10 (other mobile platforms in metadata only with approved interactive functionality) and Play's 500-character release-note limit match the linked official pages.
Merge confidence: 5/5, docs only, and the references and language mapping check out against both consumers.
Reviewer model: claude-opus-5-5
Reasoning effort: Not exposed (the run metadata available to this reviewer does not report it)
|
Replaced by synonymdev/bitkit#4, which keeps shared store release-note guidance in the Bitkit umbrella repository. The native consumers synonymdev/bitkit-ios#1224 and synonymdev/bitkit-android#1791 now depend on that PR. The shared release QA method and test archives remain in this E2E repository. |
Companion: synonymdev/bitkit-ios#1224, synonymdev/bitkit-android#1791
Release-note generation can carry another mobile platform's name into App Store metadata, and translated or reused copies can retain the same problem. Add one shared method for drafting and checking store notes before generation and before an authorized submission/resubmission.
Description
QA Notes
Setup
N/A — documentation only.
Journeys
N/A — no app/runtime behavior changes.
Manual Tests
N/A — no device testing required.
Automated Checks
git diff --check.Evidence
Official Apple/Google policy pages checked on 2026-11-05. Independent review of the three-repository candidate found no actionable findings.
Gaps
The consumer PRs must merge after this guide. No store submission, app build or runtime test was performed as part of this documentation change.
Models used
gpt-6.1-sol(reasoning:high)gpt-6.1-sol(reasoning:high)gpt-6.1-sol(reasoning:high)