Skip to content

v2.3.0

Latest

Choose a tag to compare

@github-actions github-actions released this 25 Aug 11:33
· 1 commit to main since this release
Immutable release. Only release title and notes can be modified.
66b0359

Three things: tools that make submitting a version easier, a safe way to handle store text in many languages, and a way to see what your API key is actually allowed to do.

Submitting a version is one step now. It used to take three separate calls in a specific order — and if you stopped after the first one nothing was submitted, though it looked like it had been. release__submit does all three in order and tells you which step actually reached Apple.

Before that, preflight__check_version answers "is this version ready to submit?" — is the build processed, is export compliance answered, is the demo account filled in, which language is missing a description. One call, and each gap names the tool that fixes it. release__submit runs this on its own and refuses to submit if something is missing.

Three tools for store text across languages. Audit, draft translation, and bulk apply. None of them writes on its own judgement — the audit reports gaps and stops, the draft only covers languages you name, and the write reads values from a CSV or JSON file you prepared. Keywords especially: the right Turkish keywords are not a translation of the English ones, they are what Turkish users search for. That decision stays yours.

You can now ask what your key can reach. Apple never tells you an API key's role, so you usually found out you had a narrow key from an error in the middle of a task. Add check_capabilities: true to asc__status and it probes five areas and reports which ones answer.

Alongside it, the guide gained a "which role do you actually need" section: App Manager covers day-to-day work, Admin is only needed for user management and the first analytics report, and no API key at all reaches the contracts, tax and banking page.

Also, an unsigned agreement is now told apart from a narrow key. Both returned the same error, but one is fixed with a new key and the other only by the account holder signing the agreement.

Three workflows as slash commands. Your client surfaces them as prompts: release-readiness (check the version, diff the store text, end in GO or NO-GO), review-triage (briefing, triage, a drafted reply per review), and price-check (worldwide prices, then what looks unintended). Each stops before the write — submitting, replying and changing a price stay yours. A prompt only appears when every tool it needs is loaded.

Two more reads. asc__account_status answers "what is waiting on me?" across your apps in one call. listing__diff_metadata shows what changed in the store text between the live version and the one you are preparing, language by language.

Smaller things. Tool search improved noticeably — 54% of real phrasings now find their tool in the top three, up from 31%. The confirmation prompt names the app it is about to change instead of showing an ID. You can pass apps by name or bundle ID, not just the number. And there is now a .mcpb bundle for installing from Claude's Connectors menu.