chore: prepare Wistia plugin 1.0.0 branding - #3
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
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.
Context / Why
Cursor’s publisher form requests a 1:1 SVG or PNG with a background plate. The existing plugin asset is a horizontal wordmark, so this prepares the official Wistia plugin’s marketplace branding and establishes its first public release version before submission.
How
1.0.0.$schemaindependently pinned to specification version1.0.0.Testing
Validation
Validated locally at 512px and 64px (2026-09-02) — PASS
Caveat: the asset has not yet been rendered by the published Cursor Marketplace listing.
Steps