Skip to content

fix(update): Store updates are offered whatever number comes with them, and the resident comes back after one - #94

Merged
rgdevment merged 4 commits into
mainfrom
fix/store-update-offers
Nov 10, 2026
Merged

rgdevment merged 4 commits into
mainfrom
fix/store-update-offers

Conversation

@rgdevment

Copy link
Copy Markdown
Owner

A copy from the Microsoft Store now offers the update the Store has, and the resident comes back by itself after the Store replaces it. This is the same fix Tisty shipped in its #580 and #582.

Why

StorePackageUpdate.Package describes the package installed here, not the one coming, so its number is never ahead of the running copy. from_the_shop threw every Store offer away as not newer, without a word.

What changes

  • The offer carries no number. If the Store offers something, About says «Microsoft Store has a new version» with the Update button, whether or not the version is known.
  • Which version: a Store copy reads the Store's public listing (displaycatalog.mp.microsoft.com, product 9N9F7C8Q43KC, fixed market and language). Packages for another architecture are skipped. If the listing cannot be read, the signed feed stands in. Nothing is installed from either.
  • New states: already downloaded and waiting for LinkUnbound to close, queued in the Store, paused there (with an «Open Microsoft Store» button), and listed but not offered to this computer yet. A copy the Store did not sell is told the Store does not update it.
  • Rationed looks: the Store allows few real checks a day. Opening the window spends one and never waits. Only «Check now» waits, up to 75 s, watching the staged package and the Store's queue, which cost no check. If the Store does not answer a press, the window says so (updateUnanswered).
  • The resident comes back: RegisterApplicationRestart with --hushed, limited to being closed for replacement (no crash, hang or reboot). Only the copy that stays as resident registers.
  • PRIVACY.md names the catalog request and the feed that stands in for it, since a Store copy no longer only talks to the Store.
  • lib.rs and the resident's main.rs shrink, and oversized.txt follows them.

How it was checked

  • cargo test for linkunbound-settings, linkunbound-shell and linkunbound-win; clippy with -D warnings; cargo fmt --all --check; scripts/rules.sh.
  • npm test (209), biome check and tsc --noEmit in app; markdownlint.
  • The Store's decisions are pure functions (shop::verdict, update::listed, update::ahead), with a test for each shelf against each thing that can be known.
  • The real catalog answer (36 KB, under the 256 KB cap) names rgdevment.LinkUnbound-BrowserPicker_2.9.0.0_x64__kdjgfdc2rb3gc, which is what the parser reads.
  • A Windows test reads the restart line and flags back with GetApplicationRestartSettings.

Not checked: a real Store update. That needs a copy with this change installed behind a newer Store release. The update that delivers this change will not reopen the resident, because the copy being replaced is the old one.

@rgdevment
rgdevment merged commit 5aa5b24 into main Nov 10, 2026
8 of 16 checks passed
@rgdevment
rgdevment deleted the fix/store-update-offers branch November 10, 2026 14:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant