Asset Goes Here Docs Sign in
ContentsVersion history
Request and review

Version history

Every time an asset is published, Asset Goes Here keeps the file it published as a numbered version: v1 is the first, and the newest is the one published now. When someone asks "can we go back to the old one?", you can look at the earlier versions and restore one without downloading it from the repository's history and delivering it again.

What's kept

PlanPublished versions kept for each asset
Free and SupporterThe version published now and the one before it. When a newer one is published, the oldest is deleted.
Pro, Team and EnterpriseEvery version.

Kept versions count toward the project's storage. The asset page says when older versions weren't kept, with a link to upgrade. Rejected deliveries are kept as before, and are separate from published versions.

Assets published before version history existed start their history with their next publish. The file they had published becomes v1 then.

See the versions

Restore one

Restoring makes an earlier version the asset's accepted file again, with the provenance and made-by it was published with. Nothing is deleted: the version published now stays in the list, so you can go back to it the same way.

Admins and developers can restore. The asset must be published, with nothing newer in progress: undo an unpublished acceptance, and wait for an open pull request to merge or close first.

A restored file goes out with the next publish like any acceptance, and that publish adds it as a new version. Until then, Undo on the asset page, agh review <asset-id> --undo or review_delivery with unaccept puts back the published file.

For agents: this page as Markdown is at /docs/version-history.md, and the CLI prints it with agh guide version-history.