riverbankcms 0.30.1 → 0.31.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -317,6 +317,7 @@ If unrelated local files would be included by a broad scope, stage a temporary c
317
317
  | `--no-meta` | Skip writing `.meta/` and media manifest files (content files still written) |
318
318
  | `--diff` | Show human-readable field-level diff with before/after values (requires `--dry-run`) |
319
319
  | `--verify-noop` | After an applied push, re-fetch the target and fail if changes remain |
320
+ | `--bookings move\|cancel` | For event schedule changes, explicitly move eligible bookings within the same civil week, or cancel all affected bookings. Omit to refuse changes affecting bookings. |
320
321
  | `--notify` | For event pushes, email the people booked on a run whose venue changes (off by default) |
321
322
  | `--delete-missing` | **[Deprecated]** Use `--delete-orphaned` instead |
322
323
 
@@ -966,6 +967,19 @@ riverbankcms event occurrence cancel summer-fest summer-run <occurrence-uuid>
966
967
  riverbankcms event occurrence delete summer-fest summer-run <occurrence-uuid> --yes
967
968
  ```
968
969
 
970
+ Schedule syncs refuse changes that would move or cancel existing bookings unless you
971
+ choose a booking action explicitly. Use `riverbankcms push events --bookings move`
972
+ (or `riverbankcms push all --bookings move`) to move eligible bookings to their
973
+ replacement in the same civil week; bookings without an eligible replacement are
974
+ cancelled as reviewed. Use `--bookings cancel` to cancel every affected booking.
975
+ `--yes` and `--force` do not choose a booking action. If a reviewed move is refused
976
+ while saving, its booking stays on the original date, which remains an exception.
977
+
978
+ The same flag works with a direct write:
979
+ `riverbankcms event upsert yoga --file yoga.json --bookings move`.
980
+ SDK callers send `bookings: 'move' | 'cancel'` on each affected member of `runs`.
981
+ This is request consent, not a schedule setting: pulled files do not remember it.
982
+
969
983
  `event upsert` and `push events` accept canonical event files with `path` and `blocks`. Events use native page authority: an `eventOffering` or `eventSeries` subject owns a page surface, and that surface owns its route, field content, publication state, and slots. `path` updates the page-surface route. `blocks` maps slot keys to surface-slot blocks, for example `blocks.main` for the built-in event template. Use stable block identifiers so repeat pushes update existing slot blocks safely. Unknown slot keys or block kinds fail validation; default slots accept enabled SDK `custom.*` blocks, while explicit template `allowedBlocks` lists remain authoritative. Ordinary editorial entries continue to use the separate `entry` commands and content-entry model described above.
970
984
 
971
985
  When the Event page is online, a push publishes the page once its content, route, identity and blocks are written, so everything pending on the page goes live, including anything saved as a draft in the dashboard. The same publish updates the image shown in run listings. While the page is offline, a push saves a draft that goes live when the page is put online. A push whose content matches the page writes no new content.