Feature/auto update#120
Open
ImBada wants to merge 1 commit intotechartdev:mainfrom
Open
Conversation
Owner
|
I also think the same. Lets leave it as sample if somebody wants it in his fork. |
ImBada
force-pushed
the
feature/auto-update
branch
from
08f1dd5 to
dc85b80
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I believe using this is highly dangerous, so it is best not to add it. I have fixed it for now and will leave it available for those who want it. Please leave it as is.
Summary
Background
Previously, updating OpenClaw required manually updating the add-on image. With this change, simply restarting the add-on triggers an automatic update via npm — no rebuild needed.
After a version upgrade, certain config keys may become invalid or renamed. The openclaw doctor --fix step detects and corrects these legacy config issues before the runtime starts, preventing startup failures.
Testing
Verified stability across two consecutive automatic upgrades:
Both upgrades completed successfully on restart with no manual intervention. The doctor fix step correctly handled config key migrations in each case.