Publishing to Store

Store only accepts project versions that were already published to the Server. Before publishing, confirm:

1. The project was uploaded to the Server and has an x.y.z version.
2. The current account can manage the project and download its source; both permissions are required.
3. The archive does not contain .env, .git, node_modules, keys, or other credentials.

Create an entry

You can start from three places:

• Run "Publish project to Store" in Studio; it carries the current project ID and version.
• Open the publish page on the Store site and pick a project and version manually.
• Create or resume a draft from the Server Web project console.

Fields:

Field	Limit
Title	120 characters
Summary	280 characters
Description	30,000 characters
Requirements	10,000 characters
Screenshots	Up to 6, PNG / JPEG / WebP, 5 MiB each
Uses System AI	Publisher declaration, checked during review

Drafts can be saved at any time. An entry can have only one open draft or pending revision; creating another returns the existing pending revision.

Submit and snapshot

On submit, the platform:

1. Reads the published source archive for that version.
2. Checks the archive structure, size, paths, and likely credentials.
3. Extracts dependencies from package.json and records technical metadata.
4. Freezes the archive and records integrity information for review and download.

Review applies to the archive at submission time. Later project changes on the Server do not alter a pending submission; publish a new version instead.

Review states

draft       saved, visible only to the publisher
pending     submitted, waiting for an admin
approved    approved, becomes current, and is listed
rejected    rejected with a required reason
withdrawn   withdrawn by the publisher or by an unlist
unlisted    derived state: the entry is not listed

Review happens in the management console. Approval re-checks archive integrity; a failed check does not switch the current version.

While a new version is under review, the previous approved version stays downloadable. The current version switches only after approval.

Rejection, withdrawal, unlisting

• Reject: the admin must provide a reason. The publisher sees it, fixes the entry, and resubmits.
• Withdraw: the publisher can withdraw a pending revision and edit it again.
• Unlist: the publisher or an admin can unlist an entry. This hides the entry and withdraws any pending revision; approved release records are kept, but the public page is hidden.
• List again: submit a revision and pass review.

Archive limits

Limit	Value
Compressed size	100 MiB
Expanded size	512 MiB
Entries	100,000
Screenshots	6 × 5 MiB

Archives must be gzip tar and may not contain absolute paths, .., Windows drive letters, duplicate paths, symlinks, or special files. Runtime directories and common credential patterns are rejected.

Common questions

Symptom	What to do
No publishable projects	Confirm the project is on the Server and the account has management and source-download permissions
The same version cannot be submitted again	Approved versions are immutable; publish a new x.y.z version
An entry already has a pending revision	Resolve or withdraw that draft/pending revision first
Archive validation failed	Check for symlinks, unsafe paths, or credentials, then publish again
Screenshot upload failed	Confirm each file is under 5 MiB and is PNG / JPEG / WebP
The submission is missing	Refresh the page; if it still does not appear, ask an admin to check the review queue