feat: change openclaw upgrade logic#12324
Conversation
|
Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 2cb6279d6f
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| if strings.TrimSpace(fromVersion) != openclawHTTPSVersion { | ||
| return false | ||
| } | ||
| return common.CompareVersion(strings.TrimSpace(toVersion), openclawHTTPSVersion) |
There was a problem hiding this comment.
This gate uses common.CompareVersion on toVersion, but that comparator returns false for non-numeric versions like latest. The codebase already treats latest/non-numeric app versions as valid upgrade targets (for example in OpenClaw HTTPS version checks), so an upgrade from 2026.3.13 to latest will skip the Caddyfile rewrite and keep the stale file this change is trying to replace.
Useful? React with 👍 / 👎.
2 participants
No description provided.