Gate release publication on live Store preflight - #21
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
1 participant
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.
The v0.1.03 workflow published the GitHub release before its Store preflight rejected the initial draft. Add an authenticated, read-only Store preflight against the same run’s MSIX before publication, so a known Store blocker stops GitHub publication when Store delivery is enabled. The submit job keeps its second preflight to detect intervening changes. Disabled Store delivery and non-tag dispatch retain their existing behavior; failed or cancelled prerequisites cannot publish.
Store failures now report Failed, the observed allowlisted API state, and the submission ID instead of leaving a misleading Validated summary. Unknown API status text is redacted. The activation record documents that v0.1.03 was submitted through the portal and defines the live evidence needed before claiming automation is verified.
Validation: 52 Python tests passed, two POSIX-only tests skipped on Windows; actionlint 1.7.12 passed; publication-condition checks passed across 8,192 combinations of job results, Store enablement, ref type and cancellation; git diff --check passed.
This change does not claim a successful live API upload/commit. The current Store certification remains untouched. After the first version is certified and deliberately published, the next reviewed higher-version tag must complete preflight, API upload and commit without a browser fallback; retain its submission ID, version and MSIX hash and verify the matching Partner Center state.