Release Summary
This release finalizes the next patch step after 4.0.6 by aligning project version defaults to 4.0.8 and keeping maintenance-mode behavior and endpoint messaging consistent for production users.
- Project version defaults now target 4.0.8 in runtime and SDK package metadata.
- Landing and availability defaults are set for normal operation while preserving fallback endpoint guidance.
- Release messaging keeps the same operational safety model introduced in 4.0.6.
Maintenance and Availability Hardening
The maintenance gate introduced in 4.0.6 remains the foundation for traffic control and endpoint safety when the primary service is limited.
- 503 responses now consistently include alternative endpoint details for API consumers.
- Limited-mode web access continues to preserve tutorial/blog routes and blog assets.
- The root landing page still acts as the canonical status and fallback handoff surface.
SDK Track Updates
The official Python SDK remains the primary documented path, and this release now explicitly points TypeScript users to a maintained alternative package.
- Python SDK remains available through OpenMLBB with endpoint coverage aligned to API routers.
- TypeScript users now have a documented alternative: npm install mlbb-sdk.
- SDK onboarding text in docs and web UI now clarifies Python-first plus TypeScript-alternative usage.
Configuration and Donation Defaults
Configuration defaults were refreshed to match current operational expectations and support messaging.
- Availability defaults target active service mode for regular traffic conditions.
- Support message baseline now reflects donation minimum guidance from $5.
- Date/version metadata in config has been moved forward for the 4.0.8 release line.
Upgrade Guidance
No major API route break is introduced in this patch. Existing clients can upgrade with minimal friction.
- If you use OpenMLBB, update to the 4.0.8 package version and re-validate your environment defaults.
- If your project uses TypeScript, evaluate mlbb-sdk as an alternative client integration path.
- Keep fallback endpoint handling in your client for limited-mode or high-traffic windows.