Skip to content

Treat Edge InProgressSubmission as a clean skip#109

Merged
gilgold merged 1 commit into
mainfrom
ci/edge-inprogress-skip
Jun 10, 2026
Merged

Treat Edge InProgressSubmission as a clean skip#109
gilgold merged 1 commit into
mainfrom
ci/edge-inprogress-skip

Conversation

@gilgold

@gilgold gilgold commented Jun 10, 2026

Copy link
Copy Markdown
Owner

Summary

Follow-up to #108. The version-match guard can't catch the in-review window (the Edge listing still shows the old version while a submission is being certified), so merges during that window failed with InProgressSubmission — as seen on the latest main run.

The publish step now inspects the failed operation's errorCode: InProgressSubmission logs "a previous submission is still in review" and exits 0, since the version is already on its way to the store. Every other failure (validation errors, timeouts, anything else) still fails the run.

🤖 Generated with Claude Code

When a previous submission of the same package is still in Edge's
review queue, the publish API rejects with InProgressSubmission.
The version is already on its way to the store, so exit 0 instead
of failing the run. All other publish failures still fail.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@gilgold gilgold merged commit b9c6e08 into main Jun 10, 2026
3 checks passed
@gilgold gilgold deleted the ci/edge-inprogress-skip branch June 10, 2026 18:08
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