Skip to content

Track last execution time for idempotent seeds#1017

Merged
markstory merged 1 commit into5.xfrom
feature/track-idempotent-seeds
Feb 4, 2026
Merged

Track last execution time for idempotent seeds#1017
markstory merged 1 commit into5.xfrom
feature/track-idempotent-seeds

Conversation

@dereuromark
Copy link
Member

@dereuromark dereuromark commented Feb 2, 2026

When using seeds it became clear that idempotent ones also need to be tracked. This clarifies actual runtime of seeds.
Also, it needs to be more transparent which ones already run and which ones aren't - and on run which actually will run.

Summary

  • Idempotent seeds now track their last execution time in the cake_seeds table (delete + insert to update the timestamp each run)
  • seeds status shows an (idempotent) marker next to idempotent seeds
  • seeds run confirmation list only shows seeds that will actually execute, with (idempotent) markers
  • Already-executed non-idempotent seeds are silently skipped (no more "already executed" output noise)
  • --fake now works for idempotent seeds (records execution without running)
  • Updated docs in seeding.rst to reflect the tracking behavior

Idempotent seeds now record their last run in the cake_seeds table
instead of opting out of tracking entirely. This gives visibility
into when they last ran via the status command. Non-idempotent seeds
that were already executed are now silently skipped instead of
printing "already executed" messages.
@dereuromark dereuromark requested a review from markstory February 2, 2026 17:34
@markstory markstory merged commit 6d5a3df into 5.x Feb 4, 2026
14 checks passed
@markstory markstory deleted the feature/track-idempotent-seeds branch February 4, 2026 19:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants