Skip to content

docs(dist): make the Microsoft Store the recommended Windows route - #285

Open
EtienneLescot wants to merge 1 commit into
mainfrom
docs/store-first-distribution
Open

docs(dist): make the Microsoft Store the recommended Windows route#285
EtienneLescot wants to merge 1 commit into
mainfrom
docs/store-first-distribution

Conversation

@EtienneLescot

@EtienneLescot EtienneLescot commented Aug 5, 2026

Copy link
Copy Markdown
Collaborator

Replaces #283, which tried to buy the problem away by signing the .exe.

What I verified first

Both Windows artifacts leave CI unsigned. Checked with Get-AuthenticodeSignature against the actual 1.8.0 build artifacts:

Openscreen.Setup.1.8.0.exe   -> NotSigned
Openscreen.Setup.1.8.0.appx  -> NotSigned

The AppX being unsigned is not a defect: Microsoft signs Store submissions during certification, and that signed copy exists only in the Store. It is never handed back, so it cannot be redistributed.

Two consequences that decided the approach:

  • Shipping the .appx instead of the .exe would be worse, not better. Windows runs an unsigned .exe after a SmartScreen prompt; it refuses outright to install an unsigned MSIX/AppX, because sideloading needs a signature the machine already trusts. We would trade a file that warns for a file that will not install.
  • The Store is therefore the only Windows route with no SmartScreen interstitial — and it is already paid for through the developer account.

What changes

The README recommends the Store first, with winget install --source msstore OpenScreen as the terminal equivalent, and keeps the .exe as an explicitly documented fallback for people who cannot reach the Store (LTSC, managed machines, offline installs, older versions).

The fallback gets an explanation rather than an apology. SmartScreen attaches reputation to the file hash while an installer is unsigned, so every release starts untrusted no matter how popular the previous one was, and there is no signature for a cautious user to verify. Users hitting that dialog deserve to know which of those it is; guessing is worse for them than being told.

What I did not build

publish-winget.yml already exists and does exactly what a winget CI job should. It has simply never run: it gates on vars.WINGET_IDENTIFIER != '', and neither that variable nor WINGET_ACC_TOKEN is set, so every release has reported skipped — stable ones included.

skipped  v1.9.0-rc.2
skipped  v1.9.0-rc.1
skipped  v1.8.0

I left it dormant on purpose rather than switching it on in passing. winget-releaser submits the NSIS .exe to the community repository, and that installer is unsigned — so turning it on adds a second, unsigned route next to the signed Store one. That is a distribution decision, not a variable to flip, so the docs now say so.

Docs

build-and-packaging.md records that no Windows signing exists in the repo at all, with the signature table above and the AppX-is-not-a-substitute reasoning, so the next person to have this idea finds the answer instead of re-deriving it. release-and-secrets.md records the dormant winget state and what turning it on would actually publish.

Sequencing — do not merge before the Store listing is live

The README will link to apps.microsoft.com/detail/9MXQ1HQJL5G5, and the submission is still a draft, waiting on the 1.9.0 final AppX. Merging earlier advertises a dead link and a winget command that resolves to nothing. Worth confirming the URL against Partner Center's product-identity page at that point too.

Buying a certificate is not foreclosed by any of this — it now smooths a secondary path rather than the only one, which makes it a comfort call once install traffic shows how much the fallback is actually used.

Summary by CodeRabbit

  • Documentation
    • Updated Windows installation guidance to recommend the Microsoft Store, with GitHub Releases and standalone installers available as alternatives.
    • Added instructions for installing via the Microsoft Store and winget, including automatic updates and signing details.
    • Documented SmartScreen warnings and limitations for unsigned Windows installers.
    • Clarified current WinGet publishing status and Microsoft Store package signing.

Both Windows artifacts leave CI unsigned — verified with
Get-AuthenticodeSignature on the 1.8.0 build, the .exe and the .appx alike.
Microsoft signs Store submissions during certification and that signed copy
lives only in the Store, so it cannot be redistributed.

That makes the Store the only Windows route that installs without a SmartScreen
interstitial, and it costs nothing beyond the developer account already paid
for. The README now recommends it first, with winget --source msstore as the
terminal equivalent, and keeps the .exe as an explicitly documented fallback
for people who cannot reach the Store.

The fallback carries an explanation rather than an apology: reputation attaches
to the file hash while an installer is unsigned, so every release starts
untrusted however popular the last one was, and there is no signature for a
cautious user to check. Saying so is more useful than letting people guess
whether the download is safe.

Also records two things that were true but written down nowhere: that no
Windows signing exists in the repo at all, and that publish-winget.yml has
reported "skipped" on every release because WINGET_IDENTIFIER was never set.
Turning it on would publish the unsigned .exe to the community source
alongside the signed Store package, which is a decision rather than a
variable, so the note says as much instead of just listing the secret.

Buying a certificate stays open and is not foreclosed here; it now smooths a
secondary path rather than the only one.
@coderabbitai

coderabbitai Bot commented Aug 5, 2026

Copy link
Copy Markdown

Review Change Stack

📝 Walkthrough

Walkthrough

The documentation now recommends Microsoft Store installation on Windows, documents standalone installer limitations, records unsigned NSIS and AppX artifacts, and explains the disabled WinGet publishing configuration.

Changes

Windows distribution documentation

Layer / File(s) Summary
Windows installation guidance
README.md
The README recommends the Microsoft Store and documents winget, automatic updates, signing, standalone installer use cases, and SmartScreen handling.
Packaging and publishing status
technical-documentation/engineering/build-and-packaging.md, technical-documentation/engineering/release-and-secrets.md
Engineering documentation describes unsigned NSIS and AppX outputs, Store signing, sideloading limits, SmartScreen behavior, and the configuration required to enable WinGet publishing.

Estimated code review effort: 2 (Simple) | ~10 minutes

Possibly related PRs

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Description check ⚠️ Warning The description provides strong technical context but omits the required template sections, checkboxes, testing details, and valid related-issue syntax. Rewrite the description using all template headings, select the applicable change and impact checkboxes, document testing, and use an accepted issue reference such as "Refs #283".
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly states the primary documentation change: making the Microsoft Store the recommended Windows installation route.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches 💡 1
🛠️ Fix failing CI checks 💡
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch docs/store-first-distribution

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@README.md`:
- Line 98: Remove the Microsoft Store link from the README’s OpenScreen
installation instructions until the final 1.9.0 AppX package is live; retain the
terminal installation option and restore the link only once the Store listing
contains that package.
🪄 Autofix

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 08af2f78-9425-49d8-8a1a-761860f8f729

📥 Commits

Reviewing files that changed from the base of the PR and between 135c360 and ed3307d.

📒 Files selected for processing (3)
  • README.md
  • technical-documentation/engineering/build-and-packaging.md
  • technical-documentation/engineering/release-and-secrets.md

Comment thread README.md
Download the `.exe` installer directly from the [Releases page](https://github.com/EtienneLescot/openscreen/releases).
**Recommended — Microsoft Store**

[Get OpenScreen from the Microsoft Store](https://apps.microsoft.com/detail/9MXQ1HQJL5G5), or from a terminal:

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🎯 Functional Correctness | 🟠 Major | ⚡ Quick win

Do not publish the Store link before the final package is live.

The PR objective states that this link must not be used until the final 1.9.0 AppX is live. Remove or defer this link until the Store listing contains that package. Otherwise, users can install an incomplete or incorrect Store release.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@README.md` at line 98, Remove the Microsoft Store link from the README’s
OpenScreen installation instructions until the final 1.9.0 AppX package is live;
retain the terminal installation option and restore the link only once the Store
listing contains that package.

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