Keep imux Updated with Sparkle

Stable imux builds publish update metadata on the product host. You do not need a side installer app.

This guide explains the official feed, how in-app updates relate to the DMG, and how automation can pin versions safely.

Prerequisites

01
Know the official update URLs
- Appcast (Sparkle): https://www.iccjk.com/downloads/appcast.xml
- Manifest: https://www.iccjk.com/downloads/latest.json
- Stable DMG alias: https://www.iccjk.com/downloads/imux-macos.dmg
Only trust these hosts (and clavue.com links that point here).
02
Use in-app updates when prompted
When Sparkle offers an update, review the short version notes and install. Build numbers are monotonic (for example 332 for 5.0.34). Do not downgrade by force unless support asks.
03
Manual re-download path
If auto-update fails (network, Gatekeeper, interrupted download), grab a fresh DMG from /download or the versioned archive URL in latest.json, then replace /Applications/imux.app.
04
Automate with the manifest (optional)
```
curl -fsSL https://www.iccjk.com/downloads/latest.json | python3 -m json.tool
```
Use downloads.macos.sha256 and size to verify before deploying fleets. Prefer the versioned archive URL for pinable installs.

Nightly/debug tags from developers are not the stable Sparkle channel.
Mac release deploys are assets-only on the site; your app still updates via appcast.

Where do release notes live?

https://www.iccjk.com/changelog and the notes bundled with the Sparkle item.

Can I stay on an older build?

Yes by not accepting the update, but security and blank-terminal fixes land on newer builds (for example 5.0.34+).