What woodpecker-ci/woodpecker shipped

This week: pipelines with workflow dependency cycles now fail instead of hanging; SQLite lock errors are reported correctly; Bitbucket webhooks without an owner are rejected; Gitea and Forgejo webhook signatures are enforced; renamed pull request files are detected.

This week's changes to Woodpecker: pipelines whose workflows depend on each other in a cycle now fail instead of waiting forever, and database read errors from SQLite lock contention are reported as such rather than as missing records. Bitbucket webhooks whose repository full name has no owner are rejected instead of panicking the handler, and enabling a single repository on Bitbucket no longer requires looking up every repository. Gitea and Forgejo now enforce webhook body signatures where secrets are already stored, keep previous paths of renamed pull request files so path constraints match, and have working files pagination again. Log store errors are returned to the agent except for duplicate entries, and a new CI_FORGE_HOST variable is available.

Woodpecker 3.20.1 is out and restores drone envsubst; use it instead of 3.20.0, which had an unintended breaking change. Also this week: fixes for depends_on gates after queue reload, annotated tag commit SHAs, GitLab tag pipeline authors, and a panic on workflow save failures.

Woodpecker 3.20.1 is released and restores drone envsubst with regression tests; 3.20.0 had an unintended breaking change, so use 3.20.1. Alongside the release, several pipeline correctness fixes landed: depends_on gates no longer run and report success after a failed dependency when the queue reloads, annotated tags on GitLab, Gitea and Forgejo now resolve to the commit SHA, GitLab tag pipelines take the author from webhook metadata, and saving workflows no longer panics the server on a transient database error. Image tag detection for registries with a port is fixed, and revoked environment admins now stay revoked until restart.

This week: Kubernetes no longer reports vanished pods as successful, GitLab token rotation stops breaking running pipelines, the server survives config parse panics, agent keepalive flags work, and CI_REPO_ID is now available to pipelines.

This week in Woodpecker: the Kubernetes backend no longer reports a step as successful when a pod disappears without an observed exit status. GitLab token rotation no longer invalidates clone credentials for running pipelines. The server recovers from panics in config parsing, so user-controlled config cannot take the whole process down. The agent now applies the keepalive time and timeout flags. Org-level secret and registry retrieval is scoped more strictly. Pipelines get a CI_REPO_ID variable, and the HTTP config extension receives the restart flag.

This week: config parsing panics fixed, bearer credentials no longer logged, SQLite lock retries for pipeline creation, login page links only http(s), forced token refresh for several forges, read only fallback when permission sync fails.

This week's changes: fixed server panics while parsing config, stopped logging bearer credentials at trace level, added retries for pipeline creation when SQLite reports a locked database, restricted login page error links to http and https, forced the oauth2 token exchange in refresh for Gitea, GitLab, Forgejo and GitHub, and added a read only fallback when forge permission sync fails. Also: Kubernetes backend now errors on unparsable backend options, pipeline restarts no longer copy reviewer metadata, token expiry is persisted on existing user sign in, queue scheduling is faster, and the GitLab pull request list now uses the merge request IID.

Fixed: queue pause survives restarts, agents no longer block shutdown, step logs kept when skipped workflows end a pipeline, config race resolved, and GitLab group-inherited permissions work. Registry host:port addresses now save, and cli exec sanitizes secrets.

This week we fixed several issues affecting pipeline runs. A paused queue now stays paused after a server restart instead of resuming dispatch. Agents holding long polls no longer block a graceful server shutdown. Step logs are kept when a pipeline ends with skipped workflows, and logs arriving quickly are batched each second. Concurrent webhooks for the same commit no longer race on config persistence. GitLab projects reached only through a parent group now resolve permissions correctly. Registry addresses in host:port form can be saved, cli exec sanitizes secrets, and the API version endpoint matches the spec. A stable release with security and bug fixes also shipped.

Go 1.27 adoption complete, dependency graph storage merged for frontend visualization, GitLab status transition fixes, Kubernetes CLI exec workspace resolution, custom shell paths for local backend.

This week's updates bring significant improvements across Woodpecker CI. We've upgraded to Go 1.27 with all its enhancements. The database now stores pipeline dependencies, enabling better visualization in the UI. GitLab integration is more robust with proper status transition handling. Kubernetes users will see resolved workspace volume issues with CLI exec. Additional fixes include custom shell path support for the local backend, restored CLI completion, and corrected URL detection in logs with ANSI escapes.

New fixes: AgentList pagination in SDK, pipeline restarts after config failures, matrix env var injection prevention, multi-line secret handling, and directory filtering. Plus Linux binary installation docs.

This week's updates improve reliability and consistency across Woodpecker. The SDK's AgentList now supports pagination options properly, pipelines can restart even when configuration wasn't persisted, and matrix environment variables no longer leak into clone steps. We also fixed secret processing for multi-line content and added documentation for manual Linux binary installation with systemd service setup.