OpenClaw
-
@robi that would be nice, but very risky if many use it.
From what I can notice, in every 2-5th update, there are modifications added that are causing breakage.
So perhaps the most stable way is for @andreasdueren to push updates occasionally (example once per 1-3 months), but perform tests on his own OpenClaw and if needed modify the package so that all instances don't break when an update is automatically pushed.
-
@robi that would be nice, but very risky if many use it.
From what I can notice, in every 2-5th update, there are modifications added that are causing breakage.
So perhaps the most stable way is for @andreasdueren to push updates occasionally (example once per 1-3 months), but perform tests on his own OpenClaw and if needed modify the package so that all instances don't break when an update is automatically pushed.
-
@creative567145 said:
From what I can notice, in every 2-5th update, there are modifications added that are causing breakage.Really? Break how?
I haven't been using it, but know millions of others are.
Odd that it hasn't been solved by now.
@robi In the GitHub repository the breaking changes are listed
https://github.com/openclaw/openclaw/releasesExample (from our current version 2026.3.23 to the current one 2026.4.11):
openclaw 2026.4.5
openclaw 2026.4.2
openclaw 2026.3.31
openclaw 2026.3.28
openclaw 2026.3.24Plus regular upgrades to the system functionality, for example how the Videos are being generated.
But this is due to the setup that each client has performed before that.
For example, to be able to generate Videos via Gemini, we had to install custom skills and scripts. So when the update is applied that doesn't have that requirement, either that functionality will break the current process, or we will just need to re-adjust the configuration.Many people have reported that they are performing the breakage fixes just by connecting Claude Code via SSH and letting it do it's "magic".
-
@robi In the GitHub repository the breaking changes are listed
https://github.com/openclaw/openclaw/releasesExample (from our current version 2026.3.23 to the current one 2026.4.11):
openclaw 2026.4.5
openclaw 2026.4.2
openclaw 2026.3.31
openclaw 2026.3.28
openclaw 2026.3.24Plus regular upgrades to the system functionality, for example how the Videos are being generated.
But this is due to the setup that each client has performed before that.
For example, to be able to generate Videos via Gemini, we had to install custom skills and scripts. So when the update is applied that doesn't have that requirement, either that functionality will break the current process, or we will just need to re-adjust the configuration.Many people have reported that they are performing the breakage fixes just by connecting Claude Code via SSH and letting it do it's "magic".
@creative567145 thanks for the info, yes that would be the easiest way.
Sounds like they need to manage flavors
-
@robi that would be nice, but very risky if many use it.
From what I can notice, in every 2-5th update, there are modifications added that are causing breakage.
So perhaps the most stable way is for @andreasdueren to push updates occasionally (example once per 1-3 months), but perform tests on his own OpenClaw and if needed modify the package so that all instances don't break when an update is automatically pushed.
@creative567145 @robi What's the preference here? My original CI/CD was set up before the community apps existed so that's why there haven't been any proper package updates. I'm happy to set up the proper pipeline, but I need to know how people want me to set this up. Should I build daily? Weekly?
I'm not actually using openclaw. I had switched to nano claw early on and am now using Hermes agent. So I can't test this before pushing updates.
-
@creative567145 @robi What's the preference here? My original CI/CD was set up before the community apps existed so that's why there haven't been any proper package updates. I'm happy to set up the proper pipeline, but I need to know how people want me to set this up. Should I build daily? Weekly?
I'm not actually using openclaw. I had switched to nano claw early on and am now using Hermes agent. So I can't test this before pushing updates.
@andreasdueren The only preference is that it's stable and doesn't break on updates.
So in this case, perhaps once per month. This way, if there is a breakage that is dependent on the admin unique setup within OpenClaw, we can solve that for each client.But if a breakage origin is due to the Cloudron packaging that requires modifications, I don't know what to say...ideally somebody needs to test the updates before pushing them to all instances.
-
@andreasdueren The only preference is that it's stable and doesn't break on updates.
So in this case, perhaps once per month. This way, if there is a breakage that is dependent on the admin unique setup within OpenClaw, we can solve that for each client.But if a breakage origin is due to the Cloudron packaging that requires modifications, I don't know what to say...ideally somebody needs to test the updates before pushing them to all instances.
ideally somebody needs to test the updates before pushing them to all instances.
I've not started using any Community Apps yet myself, but I'd suggest for anything important a good pattern might be to keep auto-updates turned off and to test them first in a cloned app before applying the updates to production
-
ideally somebody needs to test the updates before pushing them to all instances.
I've not started using any Community Apps yet myself, but I'd suggest for anything important a good pattern might be to keep auto-updates turned off and to test them first in a cloned app before applying the updates to production
@jdaviescoates maybe. But honestly I’ve been running Ente fully automatically updated with CI/CD for a year? now and never had any issues whatsoever.
-
@jdaviescoates maybe. But honestly I’ve been running Ente fully automatically updated with CI/CD for a year? now and never had any issues whatsoever.
@andreasdueren but this thread is about OpenClaw and it sounds like that often has breaking changes.
-
@andreasdueren The only preference is that it's stable and doesn't break on updates.
So in this case, perhaps once per month. This way, if there is a breakage that is dependent on the admin unique setup within OpenClaw, we can solve that for each client.But if a breakage origin is due to the Cloudron packaging that requires modifications, I don't know what to say...ideally somebody needs to test the updates before pushing them to all instances.
@creative567145 @andreasdueren I would tend to agree monthly with a quick check that it's not a bad breakage release.
Otherwise might as well run it in LAMP and have it mange itself.
-
@andreasdueren but this thread is about OpenClaw and it sounds like that often has breaking changes.
this thread is about OpenClaw
Obviously, but it sounded your concerns were about community apps not OpenClaw in specific. I'll set up monthly updates then
-
this thread is about OpenClaw
Obviously, but it sounded your concerns were about community apps not OpenClaw in specific. I'll set up monthly updates then
@andreasdueren fair enough.
I guess it was really for any app (community or otherwise) where people are worried that auto updates might break things. e.g. some people have auto-updates for Nextcloud turned off as plugins often break things.
Saying that, it's so easy to roll back to backups on Cloudron it's a relatively low risk for most people I'd suggest.
-
CI/CD fires now on the 1st of each month.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login