Skip to content

fix: declare the demo recording URL in the review metadata - #13

Merged
stefanjudis merged 1 commit into
mainfrom
stefanjudis/openai-demo-recording-url
Nov 4, 2026
Merged

stefanjudis merged 1 commit into
mainfrom
stefanjudis/openai-demo-recording-url

Conversation

@stefanjudis

Copy link
Copy Markdown
Collaborator

The reupload of the portable package failed with:

Plugin upload failed
checkly-plugin-1.0.0.zip
Invalid URL (POST /v1/dashapi/uploads/plugins)

Every absolute URL in the built package parses as a valid HTTPS URL, and the relative ./assets/checkly-logo.png icon paths were present in the previous upload that succeeded. The only thing new in this package is extensions["com.openai"].review, and demo_recording_url is the one URL-typed field in it that we left out — so the endpoint most likely parses it unconditionally.

A demo recording is a hard requirement for a remote MCP submission regardless, so the URL belongs in the manifest beside the test cases it demonstrates. The ZIP test now asserts it is present and absolute.

Treat the diagnosis as a hypothesis until an upload confirms it.

Uploading the package with a review block but no demo_recording_url is
rejected with "Invalid URL (POST /v1/dashapi/uploads/plugins)". Every
absolute URL in the package parses, and the relative icon paths were in
the previous upload that succeeded, so the field the endpoint can't
parse is the one URL-typed key in review that wasn't there.

A demo recording is required for a remote MCP submission anyway, so the
URL belongs in the manifest next to the test cases it demonstrates.
@stefanjudis
stefanjudis merged commit 632076e into main Nov 4, 2026
1 check passed
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