Skip to content

feat(ci): read-only probe for Edge submission status - #14

Open
Open-Capture wants to merge 1 commit into
mainfrom
feat/edge-status-check
Open

Open-Capture wants to merge 1 commit into
mainfrom
feat/edge-status-check

Conversation

@Open-Capture

Copy link
Copy Markdown
Owner

publish: Succeeded means Microsoft accepted the submission — not that anything is live. Certification runs afterwards and the store keeps serving the previous version until it clears.

The store page can't settle it either: it renders its version client-side (curl sees no version at all), and the JSON endpoint behind it reports only what's currently public. So there was no way to distinguish "queued behind certification" from "silently rejected" except waiting and refreshing.

This queries the publish operation and the product's draft submission, and prints the live store version alongside for comparison.

Read-only — safe to run against a submission that's mid-review.

🤖 Generated with Claude Code

https://claude.ai/code/session_018GACz6WB6EKUNkUE2xSVe1

"publish: Succeeded" means Microsoft accepted the submission, not that
anything is live — certification runs afterwards and the store keeps serving
the previous version until it clears. The store page cannot settle the
question either: it renders its version client-side, so curl sees no version
at all, and the JSON endpoint behind it reports only what is currently
public.

That left no way to tell "queued behind certification" from "silently
rejected" except waiting and refreshing. This queries the publish operation
and the product's draft submission, and prints the live store version
alongside for comparison.

Makes no writes, so it is safe to run against a submission that is mid-review.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_018GACz6WB6EKUNkUE2xSVe1
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