Skip to content

fix: correct Sparkle appcast version for 2026.2.15#18201

Merged
steipete merged 2 commits intoopenclaw:mainfrom
MisterGuy420:fix/18178-macos-update-sparkle-version
Feb 16, 2026
Merged

fix: correct Sparkle appcast version for 2026.2.15#18201
steipete merged 2 commits intoopenclaw:mainfrom
MisterGuy420:fix/18178-macos-update-sparkle-version

Conversation

@MisterGuy420
Copy link
Contributor

@MisterGuy420 MisterGuy420 commented Feb 16, 2026

The sparkle:version was incorrectly set to '11213' instead of '202602150', causing the macOS app to not detect the 2026.2.15 update. Sparkle compares versions as strings, so '11213' < '202602140' (2026.2.14's version), preventing the update from being offered to users.

Fixes #18178

Greptile Summary

This PR contains two independent bug fixes: correcting the Sparkle appcast version from 11213 to 202602150 for the 2026.2.15 release, and clearing stale device-auth tokens when the gateway connection fails due to token mismatch. The appcast version fix ensures macOS users can detect the 2026.2.15 update (Sparkle compares versions lexicographically, so 11213 < 202602140). The device-auth token fix prevents persistent authentication failures after re-pairing a device.

Confidence Score: 5/5

  • This PR is safe to merge with no risk
  • Both fixes are straightforward corrections: the appcast version change uses the correct YYYYMMDD0 format matching existing entries (202602140), and the device-auth token clearing logic follows the established pattern with proper error code checking and role handling
  • No files require special attention

Last reviewed commit: e2e7827

OpenClaw Bot added 2 commits February 16, 2026 15:49
When the gateway connection fails due to device token mismatch (e.g., after
re-pairing the device), clear the stored device-auth token so that
subsequent connection attempts can obtain a fresh token.

This fixes the cron tool failing with 'device token mismatch' error
after running 'openclaw configure' to re-pair the device.

Fixes openclaw#18175
The sparkle:version was incorrectly set to '11213' instead of '202602150',
causing the macOS app to not detect the 2026.2.15 update. Sparkle compares
versions as strings, so '11213' < '202602140' (2026.2.14's version), preventing
the update from being offered to users.

Fixes openclaw#18178
@openclaw-barnacle openclaw-barnacle bot added gateway Gateway runtime size: XS labels Feb 16, 2026
@steipete steipete merged commit 6e1edc7 into openclaw:main Feb 16, 2026
26 checks passed
@sebslight sebslight self-assigned this Feb 17, 2026
@MisterGuy420 MisterGuy420 deleted the fix/18178-macos-update-sparkle-version branch February 22, 2026 21:31
@MisterGuy420
Copy link
Contributor Author

Cleaning up: deleted the branch from my fork as part of repository maintenance. This was merged—thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

gateway Gateway runtime size: XS

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug]: macOS App (2026.2.14.dmg) Does Not Detect Available Update (2026.2.15)

3 participants