Release Prepare

Use this skill when preparing a new VivaDicta release for App Store submission.

Version Format Convention

Use the full X.Y.Z form in every user-facing surface — never the short X.Y form like "3.3":

• In-app What's New screen headline field (e.g. "What's New in VivaDicta 3.3.0")
• App Store release notes body text (e.g. "VivaDicta 3.3.0 adds...")
• App Store description if it mentions the version
• Website changelog intro paragraph (the <h2> already shows 3.3.0, but the prose must too)
• LinkedIn / social post copy
• Filenames: whats-new-X.Y.Z.md, description-X.Y.Z.md, linkedin-X.Y.Z-<slug>.md

The only place short X.Y form survives is the internal WhatsNewCatalog.releases dictionary key, because the version-match logic is intentionally major.minor (so 3.3.0 / 3.3.1 / 3.3.2 all hit the same entry). That key is not user-visible.

Related Skills