v0.5.1

MMSP 0.5.1 makes google-genai the compatible client for Google's generateContent, with Vertex AI naming it, and moves the Qwen entries to Qwen3.8 27B. Vertex AI users change one argument; the compatibility notes below say which.

Highlights

• google-genai is the compatible client for generateContent, as the Google GenAI SDK speaks it, named after its wire protocol like the other compatible clients. It serves Vertex AI (the service-account JSON key as the API key), the Gemini API, and gateways that proxy generateContent. gemini-generate-content still names it, as an alias (#244).
• Vertex AI is no longer part of gemini-official. gemini-official speaks the Gemini API's Interactions endpoint only, and refuses a service-account key with an error that names google-genai, so a private key never travels as an API key (#244).
• google-genai keeps its key with its endpoint. Like the other compatible clients, it reads GEMINI_API_KEY from the environment only together with GEMINI_BASE_URL or Google's own endpoint; a base_url passed in needs an api_key with it (#244).
• Qwen3.8 27B. The registry lists qwen/qwen3.8-27b on OpenRouter and Qwen/Qwen3.8-27B on SiliconFlow in place of Qwen3.6 35B A3B (#245).
• Site and project. A pure blue brand color across the site, the mark and the images; a Design philosophy page; logo files in .github/images/; the publish workflow skips a version that is already published (#234, #237, #238, #240, #242).

Compatibility

• With a Vertex AI service-account key, pass client_type="google-genai" (clientType: "google-genai"). gemini-official, and a gemini- model id with no client type, now raise on one.
• google-genai with a base_url needs an api_key passed in as well.
• Code that imported the client by module path imports google_genai / GoogleGenaiClient in place of gemini_generate_content / GeminiGenerateContentClient.

Install

pip install mmsp==0.5.1
npm install @prismshadow/mmsp@0.5.1

Full detail: changelog/0.5.1/README.md.