Checking Your Site's Deploy History
Every Piskes site now has a full publish history: when it was last published, who published it, and whether the main line has changed since.
Every Piskes site now has a full publish history you can check at a glance: when it was last published, who published it, and how many pages went out in that deploy.
What it answers
Once more than one person can work on a site — which is now easier than ever with collaborator invites — "who published this and when" stops being a question you can answer from memory. The deploy history view answers it directly, and goes a step further: it also shows whether the main line of the site has edits since the last deploy, broken down into pages added, modified, or removed, so you can see at a glance whether what's live actually matches what's been worked on since.
How it's calculated
Rather than storing a snapshot of the site's content at each deploy, which would need its own diffing logic for a multi-page site, the comparison works by checking each page's own last-updated timestamp against the last deploy's time. It's a simpler mechanism, and it means the "changes since last deploy" view is always accurate to what's actually in the database right now, not a snapshot that could drift out of sync.
Where to find it
Deploy history is visible to anyone with at least viewer access to a site, from the site dashboard, and is also available to a connected AI assistant through the list_deploys MCP tool for anyone who'd rather ask than click through.