Release an updater beside a full resource download
Where: Resource → New revision / Files in this release
Before you start
An updater’s from/to metadata describes it; changing metadata cannot make an archive compatible with another baseline. Do not overwrite distributed archive bytes under the same version name.
Steps
- Publish the new version with a useful changelog.
- Add the full release file with an identifying label.
- Add each updater as its own file and enter Release version, Update from version and Update to version.
- Review every filename and intended baseline before publication.
- Download/check the intended files as an authorised reader.
Verify
Each file’s visible type/version/from/to agrees with its actual package and handoff.
Troubleshooting
If a user has another baseline, supply its exact updater or supported upgrade path. Keep premium-file entitlement on every revision/extra-file endpoint.
