openclaw - 💡(How to fix) Fix Feature Request: Add production-readiness stability label to releases [1 comments, 2 participants]

Hi Peter 👋

First off – thank you for OpenClaw. We've been running it as a family and business assistant (Telegram integration, automations, cron jobs, Home Assistant control) and it has genuinely become part of our daily workflow. Really appreciate the work you and the team put into this.

The problem:

When a new release drops, it is currently unclear whether it is safe to update a production setup. For example:

• v2026.4.24 had a postinstall pruning bug (#72042) that broke gateway startup – 1617 dist files missing
• v2026.4.25 introduced the Active-Memory plugin, which caused 25-30s timeouts per message on Ollama setups (the plugin ran a blocking memory search before every reply)
• The MyClaw newsletter warned "do not upgrade to 4.24" – but this critical info was not in the release notes themselves

We run OpenClaw in production and cannot afford to install every update just to find out it breaks our setup. Right now we have no reliable way to know which versions are safe.

Proposal:

Add a simple stability indicator to each release, for example:

• ✅ Production-ready – tested and safe for daily-use / production setups
• ⚠️ Early adopter – new features, may have edge cases or plugin compatibility changes
• 🔴 Known issues – wait for next patch before updating

This could be:

• A line at the top of the release notes body
• A GitHub release label or tag
• A stability field in release metadata

For users who rely on OpenClaw for real work (not just experimentation), this single piece of information would save hours of troubleshooting and downtime. We would only update when a release is clearly marked as production-ready.

Thanks for considering! 🦞

Context: Running OpenClaw as a production family/business assistant with Telegram, Ollama, Whisper, Home Assistant, cron automations.