You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Publish update manifest endpoint for manual update checker #46
That remote endpoint is not available yet, so the checker currently fails safely with the "Could not check for updates" state until the web/CDN side is published.
Scope
Publish latest.json at the expected URL, or confirm the final manifest URL and update the client constant if it changes.
Point downloadUrl to the current release artifact, initially likely MicroClawInstaller.zip until a formal MicroClawSetup.exe exists.
GET https://microclaw.microsoftol.com/releases/latest.json returns HTTP 200 with valid JSON.
version is a numeric dotted version string, for example 1.0.1.
downloadUrl is HTTPS and points to a downloadable release artifact.
MicroClaw Desktop Settings > About > Check for updates can show either "up to date" or "update available" instead of failing due to a missing endpoint.
Remaining external blockers before the issue's live acceptance criteria can pass:
Enable a GitHub Actions runner for MicroClawWeb.
Add AZURE_WEBAPP_PUBLISH_PROFILE.
Publish a public, Authenticode-signed MicroClawSetup.exe release asset and update the manifest URL/SHA-256.
Repair the Azure China Front Door route/origin/WAF configuration for microclaw.microsoft.com.
The current Actions installer was not used because it is authenticated-only and unsigned. The deployment path remains fail-closed rather than publishing an invalid update manifest.
Activity
angnuoli commentedon Aug 19, 2026
Implementation progress:
UPDATE_MANIFEST_URLfrom the obsoletemicroclaw.microsoftol.comhost to canonicalmicroclaw.microsoft.comweb.config, and deployment documentationaka.ms/MicroClaw-Installertarget because it resolves to HTMLVerified live status on 2026-08-19:
https://microclaw.microsoft.com/-> Azure China Front Door HTTP 403CONFIG_NOCACHEhttps://microclaw.microsoft.com/releases/latest.json-> HTTP 403https://microclaw.microsoftol.com/releases/latest.json-> IIS HTTP 404Remaining external blockers before the issue's live acceptance criteria can pass:
MicroClawWeb.AZURE_WEBAPP_PUBLISH_PROFILE.MicroClawSetup.exerelease asset and update the manifest URL/SHA-256.microclaw.microsoft.com.The current Actions installer was not used because it is authenticated-only and unsigned. The deployment path remains fail-closed rather than publishing an invalid update manifest.