Repository navigation
Submit a release's MSI to the Microsoft Store from a workflow - #539
Merged
Merged
Conversation
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.
Each release needs a new Store submission whose package URL names that release's MSI. This adds a hand-run workflow that does it through the Store submission API.
scripts/release/msstore-submit.sh <tag>:netscli.com/download/<tag>/…msianswers 200 with no redirectpackageUrlon the draft's packages, keeping every other field, and commits themIt does not wait for certification.
msstore-submit_test.shruns it against a fakecurlin CI (next tolib_test.sh), covering the happy path, call order, a redirecting URL, an in-progress submission, an API error and a draft that never becomes ready.Not verified
docs/MICROSOFT-STORE.mdsection 5, which only the account owner can create.jq, which this machine lacks, so its first run is in CI.Inert until the secrets exist: the workflow only runs on
workflow_dispatch.