The simplest way to publish is to upload the signed zip yourself. If you release often, set up publishing from GitHub Actions instead.

Upload a release

1. Open Publish in the author console (choose PrusaSlicer plugin if it asks).
2. Pick the signed zip, at most 32 MB.
3. Choose the channel: stable, or beta for testers.
4. Write what changed. The release notes show next to the version.
5. Upload.

The marketplace checks right away that author in manifest.json is your author id, that the signature matches one of your active keys and, for a new plugin, that the id is in one of your namespaces. If something is wrong, you get the reason at once.

To publish a new version of an existing plugin, you can also upload it from the plugin’s page.

What happens after the upload

1. Checks. The bundle is unpacked in isolation and checked: allowed files only, no malware, nothing suspicious in the Lua code.
2. Automatic review. An AI model reviews the code against the marketplace policy.
3. Published. If everything passes, the version is published with the Unverified badge and people can install it.

If a check finds something unclear, the release waits for a person from the marketplace team. Your plugin’s page shows where each release is. A person may later review a published version and mark it Trusted.

Manage your plugin

On the plugin’s page in the author console you can:

• Edit the details: name, description, homepage, repository and category. Changes are checked before they go live.
• Delete the plugin. It leaves the catalogue and nobody can install it any more. Nothing is erased: the marketplace team can restore it, and its id stays reserved for you.