Repository navigation
feat(desktop): read Stable and Beta updates from verified mirror feeds - #967
Merged
Merged
Conversation
Contributor
Thread transfer impact✅ Thread transfer remains within every enforced ceiling.
Other scenariosAll 64 scenario measurements match All 64 scenario measurements
Baseline: Scenario and decoded snapshot size10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.
Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed. |
This was referenced Nov 16, 2026
yaacovcorcos
changed the base branch from
main
to
claude/downloads-updates-20261116
November 16, 2026 22:16
yaacovcorcos
force-pushed
the
claude/desktop-mirror-feed-20261116
branch
2 times, most recently
from
November 16, 2026 22:34
fa67901 to
221cdec
Compare
Running apps now check ScientFactory's generic electron-updater feeds instead of the GitHub release indexes: - Stable: https://downloads.scientfactory.com/scient-desktop/updates/stable - Beta: https://downloads.scientfactory.com/scient-desktop/updates/beta The website's release mirror publishes these only after every file they name is in its immutable version directory. Nightly keeps GitHub, which the mirror does not carry. Like GitHub's provider, the feed downloads differences with single range requests. Unchanged: an administrator's policy feedUrl still wins on every channel; the app-update.yml baked at build time still names GitHub (publisher compatibility for older clients and the build's publish config); Windows publisher verification still reads publisherName from that installed app-update.yml, so signature checks do not depend on the feed. Do not merge until the mirror feeds are deployed, populated and verified (ScientFactory-website release-mirror runbook): before then every check would fail with a missing channel file. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
yaacovcorcos
force-pushed
the
claude/desktop-mirror-feed-20261116
branch
from
November 16, 2026 22:42
221cdec to
3726dbc
Compare
… serve A check the mirror cannot answer runs again against GitHub in the same check; a download the mirror fails leaves the rest of the run on GitHub. Every release is on GitHub, so an app never strands on a missing or broken mirror feed. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ed-20261116 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… UPSTREAM.md Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…hed mirror electron-updater downloads from the provider its last check used, so the background retry after a mirror download failure first checks GitHub. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… download fails A failed GitHub check left electron-updater downloading from the mirror, but the retry guard read the feed already selected and stopped re-checking. Track the owed GitHub check separately and clear it only when GitHub answers. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Stable and Beta apps now check Scient's verified mirror feed (
downloads.scientfactory.com/scient-desktop/updates/{stable,beta}) for updates instead of GitHub. Nightly still uses GitHub, administrator overrides still take precedence, and Windows publisher verification and build-time publishing metadata are unchanged. Differential downloads use single-range requests.Outcome attribution follows the feed and channel actually used. Apply outcomes omit the previous process's source, which is no longer available;
attemptReflinks back to the original handoff.GitHub fallback
The owner asked for a GitHub fallback as well as the mirror, so an app that can't reach the mirror can still update:
refreshFromGitHub). Without that, the retry would go back to the mirror.Mirror is live
Website #77 is merged, and the
scientfactory-release-mirrorworker was deployed from website main on 2026-11-17. Its cron runs have populated both feeds:Every
*.ymlmanifest (mac, Windows, Linux) and every file they list returns 200.Stack
Built on #970. Once #970 merged, this was retargeted to
mainand main was merged in with a merge commit.Verification and review
9396528c86c): rootpnpm run typecheck,vp check(0 errors), the seam check againstorigin/main, upstream provenance, and the desktop update tests (src/updatesandsrc/scient/updateOutcomes, 11 files, 146/146). All were run on macOS with Node 26.13.1.DesktopUpdates.scient.test.ts. The background-retry test fails without therefreshFromGitHubfix.779646df169).1520d6534ff, on main9b6059bcb79): seam, provenance, typecheck and the update tests (147/147) pass. The diff against main is the 8 feed files only.Platforms
Documentation impact
Updated the existing managed-policy documentation and the fork seam note in
UPSTREAM.md, which now mentions the fallback. No UI change.🤖 Generated with Claude Code