Requirements

Item release requirements

Prepare complete updates, write clear changelogs, and learn when an update may need to be submitted as a new item.

Updated

Download

Keep published items current

While an item remains available, creators are responsible for monitoring its core dependencies and releasing updates when reasonably necessary for security, compatibility, or continued customer use.

Preparing an item release

Every release must provide a complete, usable replacement package rather than only the files changed since the previous version. Include the current source files, production files, documentation, and other materials customers need to use the updated item.

Test the final package from a clean copy before releasing it. Where applicable, confirm that installation, dependency installation, builds, imports, migrations, updates, major features, and included links work without relying on files or configuration left over from development.

Review core dependencies as part of release preparation. Use current stable dependency versions when reasonably possible and address obsolete, unsupported, incompatible, or insecure dependencies before they create avoidable problems for customers.

Item releases become available to customers as soon as release processing completes, without a separate review. Customers who previously licensed the item may be notified. Do not release an incomplete, untested, or incorrectly packaged update with the expectation of replacing it later.

Versions and changelogs

Use Major.Minor.Patch format. Your first release must be version 1.0.0 or higher. Increase the version number for each later release.

Each release must include a clear changelog describing relevant new features, bug fixes, compatibility changes, improvements, removals, and other customer-facing changes. Write for customers rather than using only internal commit messages or vague entries such as "minor changes."

Identify breaking changes, removed features, changed requirements, and migration or upgrade steps prominently enough for existing customers to understand how the release affects them.

Coordinating listing and preview changes

Immediately before releasing an update, revise the item listing and, where applicable, the preview so the changes are ready for existing and prospective customers to view when the release becomes available. Coordinate these changes closely with the release to avoid advertising unavailable features or leaving customers with outdated information.

Review the complete listing after every material update. Update the description, compatibility selections, feature bullet points, search phrases, and other affected information so each accurately represents the released package. Replace the thumbnail, screenshots, or marketing images that no longer represent the current item.

Where applicable, confirm that the updated preview works and links back to the Wrapmarket item listing.

Item identity and replacement

An update must remain a continuation of the item customers licensed. It may modernize the design, rebuild or refactor the implementation, adopt current dependencies, and add, remove, or improve features when the result is still reasonably understood as a new version of the same item.

Describe substantial redesigns, breaking changes, and changes in technical direction clearly. Wrapmarket may require an update to be submitted as a new item when it does not preserve reasonable continuity with the existing item.

Restrictions

Creators cannot change an item's category through a release. A proposed update that belongs in another category must be submitted as a new item. Do not use an update to add a product or implementation that belongs in another category. Supplementary editable design sources described in the category guidance may continue to be included.

Wrapmarket may administratively reclassify an item after publication to correct an inaccurate assignment or to maintain the marketplace category structure. Reclassification does not authorize a creator to replace the item with a different product.

Do not replace an established listing with an unrelated item or repurpose its listing history, customer base, visibility, or item group name for a different product. A change should normally be submitted as a new item when it has a different identity or primary purpose, represents a separate implementation that would be clearer as its own item, or would cause the existing listing and release history to describe a materially different product.

Do not release an update that adds an unrelated item to an existing listing, or makes a previously rejected item available through a published item.

An item that was previously rejected must not be added in whole or in part to an existing item as an update, alternate version, bonus, optional package, or other included material. Any substantially reworked version intended for publication must follow the appropriate item submission process.

Was this article helpful?