Add scheduled publishing for incidents and maintenance#396
Merged
Conversation
Introduce a `published_at` timestamp on incidents and schedules so they can be prepared ahead of time and revealed automatically at a future date. While an item's `published_at` is in the future it is treated as a draft: - Hidden from the status page, incident timeline, system status count and the public JSON API (for guests and authenticated callers alike). - Still fully visible and editable in the Filament dashboard and over the MCP server, so operators can manage what they've prepared. - Subscriber notifications are deferred until publication rather than firing at creation time. Visibility is evaluated at read time via a `Publishable` concern (`published`/`unpublished` scopes, `isPublished()`), so items appear the moment their publish time passes. The new `cachet:publish-scheduled` command (scheduled every minute) dispatches the deferred subscriber notifications exactly once, tracked by a `published_notified_at` column. The field is exposed for writes and reads across the API request data, JSON API resources, MCP create/update tools and presenter, and the dashboard forms/tables (including a "scheduled" filter). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NCuvKjgerpaWvGcmY57G95
Gate the incident and schedule API read endpoints on the *.manage token ability rather than hiding unpublished items from every caller. Guests and read-only tokens still get the published-only view (matching the status page), while tokens that can manage the resource — and full-privilege first-party sessions — can list and fetch drafts, giving API management clients parity with the dashboard and MCP. Adds a non-throwing tokenCan() helper on GuardsApiAbilities that resolves the caller through the Sanctum guard, safe to call on the unauthenticated read routes. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NCuvKjgerpaWvGcmY57G95
Add the Published At field label/header, the "published" badge placeholder, the "scheduled" filter label, and the publish helper text to every locale that carries the incident and schedule language files (de, de_AT, de_CH, es_ES, fr, ko, nl, ph, pt_BR, zh_CN, zh_TW), matching each locale's existing terminology. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NCuvKjgerpaWvGcmY57G95
Treat published_at as an always-present timestamp instead of a nullable sentinel. The migration backfills existing incidents and schedules with published_at = created_at, and backfills published_notified_at in lockstep so the publish command never re-announces historical records. Drop the migration's down() method. New records default published_at (and, for immediate publication, published_notified_at) to the creation time via a creating hook, so items published on creation are never re-announced by cachet:publish-scheduled while future-dated items still notify when their publish time arrives. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NCuvKjgerpaWvGcmY57G95
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a
published_attimestamp to incidents and schedules so they can be prepared ahead of time and revealed automatically at a future date. While an item'spublished_atis in the future it is treated as a draft.*.manageability — parity for management clients.null= published immediately (backwards compatible); a future value = hidden until then.How it works
Publishableconcern providespublished/unpublishedscopes andisPublished(). Visibility is evaluated at read time, so items appear the moment their publish time passes — robust even if the scheduler is briefly down.->published(): API index/show (incidents and schedules), the incident timeline, the status-page schedule block, direct incident/schedule URLs (404 for guests, preview allowed for logged-in staff), andStatus::incidents().*.managetoken ability via a new non-throwingtokenCan()helper, so management tokens (and full-privilege first-party sessions) can list/fetch drafts while guests and read-only tokens cannot.cachet:publish-scheduledcommand (scheduled every minute) dispatches the deferred subscriber notification exactly once, tracked by apublished_notified_atcolumn.published_atis exposed for writes and reads across the API request data, JSON:API resources, MCP create/update tools + presenter, and the dashboard forms/tables (with a "scheduled" filter).Testing
Publishablescopes.🤖 Generated with Claude Code
https://claude.ai/code/session_01NCuvKjgerpaWvGcmY57G95
Generated by Claude Code