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
chore: migrate to S3 updater endpoint (sync from ethereum/meetily) (#42)
* chore: bump version to v0.1.17
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* feat: switch updater endpoint to S3 with AzimovS fallback (#2)
* feat: switch updater endpoint to S3 with AzimovS fallback
Point tauri.conf.json's updater endpoints at the new S3-served latest.json
as primary, keeping the AzimovS GitHub Releases URL as a fallback. Pubkey
is unchanged — every existing install verifies signatures against the
baked-in pubkey, so rotating it would brick auto-update for prior releases.
Add a macOS-only CI guard in build.yml that fails the run if
entitlements.plist is missing com.apple.security.network.client. Without
this entitlement, hardened-runtime macOS binaries silently report "up to
date" forever because the updater can't reach the network from Rust.
Update the diagnostic-only debug_check_update URL in lib.rs to match the
new endpoint, so manual debugging stays consistent with the production
auto-update path.
Plan: docs/plans/2026-04-28-chore-migrate-releases-to-minio-2-private-repo-validation-plan.md
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* feat(debug): probe both updater endpoints in debug_check_update
Iterate the same [S3, AzimovS] list as tauri.conf.json so the diagnostic
shows each endpoint's status independently. A failure on the primary no
longer short-circuits inspection of the fallback — the whole point of the
command is visibility, not fallback simulation.
Endpoint list is hardcoded with a doc comment requiring it to track
tauri.conf.json. Reading the config at runtime would remove the drift
risk but adds an AppHandle dependency for a debug command that touches
the URL list once a year.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* chore: bump version to v0.1.18 (#3)
First Rig A release on the new S3 endpoint. Pairs with v0.1.19/v0.1.20
to validate two consecutive auto-updates per platform before Plan 3.
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* chore: bump version to v0.1.19 (#4)
Second Rig A release. Validates v0.1.18 → v0.1.19 auto-update via S3
endpoint on macOS. Version bump alone is the visible swap signal —
no UI churn needed.
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* chore: bump version to v0.1.20 (#5)
Third Rig A release. Validates v0.1.19 → v0.1.20 auto-update on macOS,
completing the two-consecutive-auto-updates bar before Plan 3.
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
0 commit comments