Repository navigation
feat(cms): add revision history, rollback, and publishAt timestamps - #351
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
@codex review |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: ee7b8bac3e
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Bundle size9 of 194 bundles changed.
Measured 22 packed archives separately; full report includes their compressed bytes without installed dependencies. |
|
@codex review |
|
Codex Review: Didn't find any major issues. Already looking forward to the next diff. Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
Summary
Closes #339.
Rollback reuses the normal update lifecycle, retains ownership and history, and restores slug, fields, relations and schedule. Existing
(contentTypeId, slug)reads and dependent-plugin data payloads stay intact.publishAtis scheduling metadata; applications retain publishing and visibility policy.Evidence
After: 161 CMS tests passed on the initial implementation. After review corrections, 73 focused CMS tests, 13 School tests, 9 Job Board tests and 12 Core endpoint-inventory tests pass. Coverage includes populated-SQLite migration, revision lifecycle, dependent course/job writes, denied access, slug conflicts, relations, pagination and unchanged timestamp precision. All three touched packages typecheck and build.
After: Two Chromium E2E scenarios pass again after the corrections against the generated Next.js consumer: save, inspect, cancel/confirm restore, schedule restoration/clearing, failed-history retry, older-page loading, mobile layout and Escape/focus return.
Merge Danger
Door: two-way
Apply the additive database migration before serving this plugin: new
contentRevisionmodel with unique item/version keys and a nullablecontentItem.publishAt. Existing history starts at the next write; past revisions cannot be reconstructed. Rolling application code back can retain the additive schema.Blast Radius: CMS
Content writes now append a snapshot in their transaction, including School course creation/edit/archival and automatic Job Board archival. Unedited editor schedules retain seconds and milliseconds. Old revisions incompatible with the current content schema or relation permissions fail without replacing the active entry.