Version history matters when you're upgrading, debugging, or evaluating how actively a project is maintained. Here's every major OpenClaw release, what changed, and what to watch for when upgrading.
Version 1.5.x — Feb 2025
OpenClaw 1.5.0 introduced the ClaWHub Marketplace — a hosted registry of community and official skills installable with 'openclaw skill install'. The Playwright skill, ElevenLabs skill, and Supabase skill all launched with this release.
1.5.x also added the Skills API for third-party developers to publish their own skills to ClaWHub, and improved multi-channel message routing with priority queuing.
Version 1.4.x — Nov 2024
1.4.0 was a breaking change release. The config format migrated from JSON to YAML for better readability and comment support. Run 'openclaw config migrate' to auto-convert existing JSON configs.
New features: Helm chart for Kubernetes deployment, improved OAuth token refresh for LinkedIn and Twitter channels, and the web admin interface redesign.
Version 1.0 — Sep 2024
Version 1.0 marked the first stable, production-ready release of OpenClaw. Core channels (Telegram, Slack, Discord), the base skill system, and the gateway architecture all reached stability.
Prior 0.x releases were developer previews with frequent breaking changes. If you're on a 0.x version, full re-configuration is needed to migrate to 1.x.
# Check your OpenClaw version
openclaw --version
# Update to latest
pip install --upgrade openclaw
# View changelog (if docs are installed)
openclaw docs changelogCommon Mistakes
- Not reading the changelog before upgrading — minor versions occasionally have config-level changes. A 2-minute changelog read saves hours of debugging.
- Treating community forks as equals to core — forks lag in security patches and may have diverged from the core API. Know what you're running.
- Not bookmarking the official docs — docs.openclaw.dev is the authoritative reference. Community guides (including this one) may be outdated; official docs are updated with each release.
- Missing Discord announcements — the #releases channel announces breaking changes before they ship, giving you time to prepare. Follow it.
Frequently Asked Questions
Where is the best place to get help with this topic?
The OpenClaw Discord server (#help channel) and r/openclaw on Reddit are the primary community support channels. GitHub Discussions is best for feature requests.
Is this officially supported by the OpenClaw team?
Core features are officially maintained. Community forks, third-party integrations, and ClaWHub skills vary in support level — check each project's README for maintainer status.
How often is this updated?
OpenClaw follows semantic versioning with minor releases every 4-6 weeks. Major releases are announced on GitHub, Discord, and the official blog.
Can I contribute to this?
Yes. OpenClaw is open-source and welcomes contributions. Check CONTRIBUTING.md in the GitHub repo for the process. Community skills can be submitted to ClaWHub via a pull request.
Where can I find the latest version information?
The GitHub releases page and the OpenClaw changelog at docs.openclaw.dev are the authoritative sources for version information.
Is there a community forum besides Reddit and Discord?
GitHub Discussions is the official forum for longer-form technical discussions. Some international communities also maintain Telegram and WeChat groups.
M. Kim covers the OpenClaw ecosystem, community news, and third-party integrations at aiagentsguides.com.