A published template version is a fixed snapshot of reviewed reusable work. It lets a recipient know which package they are adopting even as you continue editing the original.
Separate three kinds of change
| Change | Effect |
|---|---|
| Edit listing | Changes how the template is presented. |
| Edit source | Changes your working resource. |
| Publish a version | Creates a new reviewed reusable package. |
A source edit does not automatically change a published package. A listing description should accurately represent the version recipients can adopt.
Describe the update
Use the available Patch, Minor, or Major choice to communicate the scale of change. Explain the effect in practical terms: a corrected calculation, a new workflow, a changed setup requirement, or a substantial redesign.
Review all included resource revisions and dependencies again. A previously safe package does not make newly added private material safe to redistribute.
Respect existing remixes
An adopter's resource is independent. Publishing a new version does not silently overwrite their changes, switch their connected account, or enable new automation.
Unpublishing stops new adoption while preserving existing remixes, version history, and required financial evidence. Withdrawing a listing is separate from deleting source or shutting down a Site. Review the actual action before using it to change availability.
For creator allocations, the recorded adopted version establishes provenance; listing popularity alone does not establish an earning. See Earnings.
Example: explain a changed requirement
If a new template version adds a connected reporting workflow, describe the new account requirement and the outcome it enables. Distinguish that package change from a correction to the listing’s wording.
Existing remixes keep their own configuration and changes. Do not describe publication as an automatic upgrade for adopters. See Publishing.
Example release notes
Adds a priority field to the request workflow. Existing sample requests display Normal. New adopters should review the supplied status rules before using their own records.
Use wording that describes the actual package change and required setup. Avoid promising that existing remixes receive the update automatically; Remixing creates independent work.