chore(scripts): Submit plugin releases through the Creators Service. - #691
Draft
xespona wants to merge 1 commit into
Draft
chore(scripts): Submit plugin releases through the Creators Service.#691xespona wants to merge 1 commit into
xespona wants to merge 1 commit into
Conversation
Releases went through the marketplace app, which is behind bot protection and started blocking them. The action now uploads the zip to the plugins API itself and records the release with the Creators Service, so the admin secret is no longer needed. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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
1 participant
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
Releases went through
marketplace.framer.com, which is behind bot protection and started blocking them. The marketplace side of a release now lives in the Creators Service, so the action talks to that instead.The zip upload doesn't change hands. The plugins API already handles the file, and the action can call it directly with the token it already mints. So it uploads the zip, then sends the resulting version id on. Releases still land pending for a human to approve.
Needs the matching Creators Service endpoint deployed before this merges.
Changes
submitPluginis two calls now instead of one: upload the zip, then record the release.FRAMER_ADMIN_SECRET. The old endpoint never read it, and the new one uses the access token the script already mints.