5.6.0 — A refused deletion stops reading as a failed push

A snapshot as of 5.6.0 (released 2026-09-23). It will go stale as the app moves on — that is expected, and the living reference is the guide each section links to.

Nothing to configure. This only appears if a collection opted in to propagateDeletes, and only when Google refuses one of the deletions.

A deletion Google refuses no longer hides the push that worked

Nothing to turn on.

With propagateDeletes, deleting a record deletes the Google event too — unless Google refuses, which it does for an event that has attendees. Until now that refusal was reported in the same list as a record that could not be pushed, and one entry in that list replaced the whole message. A push that created ten events and had a single deletion declined said only “Push failed”. The ten were never mentioned.

Now the two are reported apart. The message says what the push did and which deletions were left standing, with the reason:

How to tell you have it: press Push to Google on a collection with propagateDeletes on, having deleted a record whose event has attendees. You should see the counts and a line naming the event that was kept. Before 5.6.0 you saw a failure and nothing else.

Why it was wrong rather than merely terse: the record went away here and the event is still standing there — the user has to be told that. But the rest of the push carried, and reporting the refusal as a failure threw that away.

The living reference: working from a collection.

A correction to 5.5.0’s guide

5.5.0 told you to treat propagateDeletes with autoPush as unaudited — that the scheduled sync deleted without leaving a record. That was wrong, and it was my error rather than a change since. Every deleted event is logged, one line each, carrying the event id, on both the button and the scheduled run. What the unattended run does not get is a summary: its report carries neither delete count, and the per-event lines do not name the collection.

5.5.0’s page has been corrected. The remaining thing worth knowing before you enable propagateDeletes has not changed: a Google event deleted this way is gone for every attendee, not only for you.

Also in this release

@mulmoclaude/core, the collection plugin, the markdown plugin and the shapescript plugin all moved up. Nothing to do; the first two are what deliver the fix above. The full list is in the changelog.