Pack versions and republishing

Publishing is append-only. Every time you publish, you create a new version and the old one steps aside. There is no destructive rollback, so you can republish freely without losing history.

How versions work

Each time you publish a pack, the platform creates a new published version and marks the previous published version superseded. The old version is kept, not deleted, but it is no longer the one the client sees.

Republishing after a regenerate

When you regenerate a deliverable or re-run a pack, the fix is not live for the client until you publish again. So the flow is: regenerate, review in the preview, then republish. The new publish supersedes the last one.

What the client sees

The client always sees the current published version in their Deliverables list. They never see a superseded version and they never see anything you have regenerated but not yet republished.

There is no undo that reaches into the client's view. To change what the client sees, publish a new version. The previous one becomes superseded automatically.