0.1.2 — npm metadata polish (description, keywords, badges)#1
Merged
Conversation
- description: pack high-value search terms (Google Play, MCP, Android Publisher API, Play Developer Reporting) into the first 150 chars npm shows in search results. - keywords: 14 → 27. Add mcp-server, cursor, vscode, codex, gemini-cli, windsurf, play-developer-api, play-developer-reporting, play-purchases, monetization, agentic, ai-assistant, automation, android-app. Drop 'llm' (generic). - README: add npm version + downloads + CI + Tools: 150 + TypeScript badges (parity with app-store-connect-mcp). This version exists so the first artifact npm sees is the polished metadata; 0.1.1 (regionsVersion fix) was tagged before the auto-publish workflow landed and was never published.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Pre-publish polish for the first npm release. No code change, no behaviour change.
Why 0.1.2 and not 0.1.1?
`v0.1.1` was tagged before the npm auto-publish workflow landed, so its tag-push event never triggered a publish. Re-tagging would mean moving an existing tag — cleaner to bump.
Test plan