Woodpecker CI, an open-source self-hosted CI/CD platform, has released version 3.15 with new pipeline controls, cron enhancements, Kubernetes updates, UI improvements, and bug fixes.
The primary new feature is support for an optional flag in depends_on for workflows and steps. This provides greater flexibility in defining dependencies, allowing workflows or steps to proceed when a dependency is not required for every execution path.
Version 3.15 also introduces configuration options to change default pipeline config paths and extensions. Additionally, scheduled pipelines now support timezones for cron jobs, making it easier to align CI runs with local working hours, maintenance windows, or regional automation needs without relying solely on server-side timezones.
Apart from that, the release adds the CI_PIPELINE_RERUNS environment variable and restores CI_PIPELINE_STATUS in the pipeline runtime. It also exposes step type to the step environment and introduces placeholder support for inputs.
Another very convenient new feature is that the web UI now groups step logs by command and allows them to be collapsed, making pipelines with verbose commands or multiple stages.
For Kubernetes users, Woodpecker CI 3.15 adds an option to disable service workspace volumes in Kubernetes and introduces guards to stop pipeline services after completion.
As always, the release includes several bug fixes, addressing issues such as organization lookup panic, duplicated schema linter composition errors, cancellation behavior in the local backend on Linux and macOS, a missing log close button, agent ID persistence after authentication, and GitLab webhook handling when project visibility is missing from the payload.
Security updates include improved GitLab username handling, an updated uuid dependency, and server-side storage of extracted agent IDs in the gRPC context.
For additional details, see the changelog.
Image credits: Woodpecker CI Project
