Fix cron migration note in v3 blog post (#4743)

Co-authored-by: qwerty287 <80460567+qwerty287@users.noreply.github.com>
This commit is contained in:
Robert Kaussow 2025-01-19 14:18:50 +01:00 committed by GitHub
parent f4a39dfae1
commit 8b701d6bde
No known key found for this signature in database
GPG key ID: B5690EEEBB952194

View file

@ -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