Resource releases, assets and cross-listing
This handbook defaults to the flat PHP starter. See current release and edition coverage for current changes and the separate PHP port. Earlier build references identify when a feature was documented; they are not a claim that both editions expose identical controls.
Publish a version in one submission
On your resource listing, use Update resource beside the main download control.156u replaced the separate “edit file, then add a version, then attach it again” workflow.
- Confirm the read-only current version, enter the new version and its changelog.
- Add files once in the available asset slots (up to four in this build). Select the appropriate kind: fresh installer, incremental update or supporting file, with a useful label.
- For an incremental updater, enter the exact starting version. Do not label a full install as an incremental updater.
- Optionally enable Post an update, add its title/body, and review what will be published.
- Press Publish update once. The revision, its files, current download pointer and optional announcement are saved together. The fresh asset becomes the current package and the same retained file becomes downloadable from history.
You do not upload the same file twice to make version history work. The old revision address opens this form; metadata editing remains a separate task. Only the author or authorized staff can publish.
Notes without a binary release
Use Post an update without Release a new version for an announcement only. A note-only revision may intentionally have no file; a file without a new version is refused. Add a clear explanation so readers do not mistake a note for a missing archive.
A duplicate version, missing updater baseline, invalid file, untitled announcement or unauthorized author must leave the existing release intact. Do not keep clicking Publish to overcome a refusal; read the validation message and correct that field. Files are staged/associated by the server and failed requests should not leave orphan files.
See older versions for what readers can retrieve, and Premium classification before distributing commercial content.
Staff review
Check author, visibility, selected discovery areas, version, asset kind and baseline. Cross-listing the same resource in Downloads and Marketplace should reuse its canonical files rather than create a second upload history. Do not mark a Premium product free merely to make an install/download button appear. Marketplace-owned legacy rows and core resource rows have separate identities; use the correct listing when investigating a missing file.
Current cover and discussion behavior
See resource covers and discussion links. Each retained version must keep its own file; do not serve the current archive under an unavailable historical version label.
