Skip to content

Send application/json content type on Store submission commit#151

Merged
michaeljolley merged 1 commit into
mainfrom
michaeljolley-sturdy-chainsaw
Jul 5, 2026
Merged

Send application/json content type on Store submission commit#151
michaeljolley merged 1 commit into
mainfrom
michaeljolley-sturdy-chainsaw

Conversation

@michaeljolley

Copy link
Copy Markdown
Contributor

Problem

The latest release (run 28731766511, v1.2.6) got further than before — the fileStatus-based cleanup fix (#149) correctly marked the stale packages and the PUT succeeded — but the store-submit job then failed at the commit step with:

{
  "message": "Only JSON content is accepted",
  "source": "Ingestion Api",
  "target": "mediaType"
}

Root cause

The commit call is a bodyless POST .../submissions/{id}/commit. Because there was no -Body, PowerShell sent the request with no Content-Type header, and the DevCenter Ingestion API rejects the commit unless it advertises application/json.

Fix

Pass -ContentType "application/json" on the commit POST. Verified against a header-echo endpoint that this sends Content-Type: application/json with Content-Length: 0 on a bodyless request in PowerShell 7 (the pwsh used by the runner), which is exactly what the API wants.

Progression of the store fixes

This is the last step in the flow that hadn't yet been exercised, since prior runs failed before reaching a successful commit.

The Ingestion API rejects the submission commit POST with 'Only JSON
content is accepted' (target: mediaType) unless the request advertises
a JSON content type. The commit carries no body, so PowerShell was
sending no Content-Type header at all. Passing -ContentType
'application/json' sends the header with Content-Length 0 and satisfies
the API's media-type check.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
@michaeljolley michaeljolley merged commit 623f8d9 into main Jul 5, 2026
2 checks passed
@michaeljolley michaeljolley deleted the michaeljolley-sturdy-chainsaw branch July 5, 2026 20:54
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