axodotdev / axodotdev/cargo-dist
publish-job: microsoft store
- Dominant language
- Rust
- Stars
- 2.1k
- Forks
- 149
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 32
Description
It would be nice to add publishing to the microsoft store. MS provides [an official action](https://github.com/microsoft/store-submission) for publishing `MSI` and `exe`-installers.
The disadvantage of publishing `MSI`/`exe`-installers is that installers that cause SmartScreen warnings (e.g., if they are not signed), will be rejected. To avoid this, publishing `MSIX` packages is possible, but the action does not support those (https://github.com/microsoft/store-submission/issues/12), though you can [apparently work around that](https://github.com/microsoft/store-submission/issues/12#issuecomment-1539016555). For publishing CLI-applications as `MSIX`, you also need to obtain a `HeadlessAppByPass` waiver by contacting MS, which will also add a requirement to add a privacy policy to the application. I did implement MSIX-bundling for starship at one point (https://github.com/davidkna/starship/commit/ea31911062a4e62bd88a42704ffa106854d35ac9), but did not end up publishing the app due to the privacy policy requirement. I also remember reading that the MSIX-bundle would have to be (self-)signed for publishing, but the generated MSIX-bundle wasn't rejected outright without signing after uploading it.
Contributor guide
Research direction
No repository file or test is named. Start by reviewing the microsoft/store-submission action and the referenced MSIX workaround, then locate cargo-dist's existing release-publishing entry point. Done means defining and implementing a supported Microsoft Store publishing path, including the documented MSI, EXE, or MSIX constraints.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, rust
- Domain
- release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100