From 8b701d6bdec509df5b5faa2ea0ae2f1284597230 Mon Sep 17 00:00:00 2001 From: Robert Kaussow Date: Sun, 19 Jan 2025 14:18:50 +0100 Subject: [PATCH] Fix cron migration note in v3 blog post (#4743) Co-authored-by: qwerty287 <80460567+qwerty287@users.noreply.github.com> --- docs/blog/2024-12-28-release-v3.0.0/index.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/docs/blog/2024-12-28-release-v3.0.0/index.md b/docs/blog/2024-12-28-release-v3.0.0/index.md index 892347afa..2494eb121 100644 --- a/docs/blog/2024-12-28-release-v3.0.0/index.md +++ b/docs/blog/2024-12-28-release-v3.0.0/index.md @@ -105,10 +105,9 @@ There is no option yet to auto-delete old pipeline logs after a specific time or Please follow [#1068](https://github.com/woodpecker-ci/woodpecker/issues/1068) for future updates. ::: -## Migration to 5-char CRON syntax +## Migration to standard Linux CRON syntax -The underlying CRON package was changed to one that now uses the (more common) 5-char CRON syntax. -Users needs to actively updated their CRON entries, otherwise existing pipelines will error during execution. +CRON definitions now follow standard Linux syntax without seconds. An automatic migration will attempt to update your settings - ensure the update completes successfully. ## Known Issues