\r\n\n\n### Steps to reproduce\n\n.\n\n### Expected behavior\n\n_No response_\n\n### System Info\n\n```shell\n\"next-d126cf9e35\"\n```\n\n\n### Additional context\n\n_No response_\n\n### Validations\n\n- [X] Read the [docs](https://woodpecker-ci.org/docs/intro).\n- [X] Check that there isn't [already an issue](https://github.com/woodpecker-ci/woodpecker/issues) that reports the same bug to avoid creating a duplicate.\n- [X] Checked that the bug isn't fixed in the `next` version already [https://woodpecker-ci.org/faq#which-version-of-woodpecker-should-i-use]",[2904,2905],{"name":2868,"color":2869},{"name":2906,"color":2907},"ui","46DEA2",4677,"`tag` pipelines are missing avatar and commit title","2025-01-12T06:19:42Z","https://github.com/woodpecker-ci/woodpecker/issues/4677",0.7701455,{"description":2914,"labels":2915,"number":2920,"owner":2874,"repository":2875,"state":2876,"title":2921,"updated_at":2922,"url":2923,"score":2924},"### Component\n\nagent\n\n### Describe the bug\n\nDue to the nature of the GKE Autopilot cluster and my budget limit I have to configure the storage as RWO. The problem is that several pods can potentially be created at different nodes. This causes the volume not to be released until the pod of the corresponding step is finished.\nIn case is a service pod that does not terminate until the end of the workflow it can have the volume forever and end up giving timeout.\nWould it be possible not to mount volume in the services?\n\n### Steps to reproduce\n\n1. Install Woodpecker CI server and kubernetes backend agents with the helm chart.\n2. Run a repo pipeline with parallel steps and a service.\n\n### Expected behavior\n\nI would like the workflow not to get stuck when a service attaches the volume. We could avoid this by making it optional to mount the volume on the service.\n\n### System Info\n\n```shell\nWoodpecker CI 3.0.1\nGKE Autopilot 1.30.8-gke\n```\n\n### Additional context\n\n_No response_\n\n### Validations\n\n- [x] Read the [docs](https://woodpecker-ci.org/docs/intro).\n- [x] Check that there isn't [already an issue](https://github.com/woodpecker-ci/woodpecker/issues) that reports the same bug to avoid creating a duplicate.\n- [x] Checked that the bug isn't fixed in the `next` version already [https://woodpecker-ci.org/faq#which-version-of-woodpecker-should-i-use]",[2916,2917],{"name":2868,"color":2869},{"name":2918,"color":2919},"backend/kubernetes","bfdadc",4795,"FailedAttachVolume with K8s backend in GKE Autopilot","2025-03-18T13:46:26Z","https://github.com/woodpecker-ci/woodpecker/issues/4795",0.77111644,{"description":2926,"labels":2927,"number":2934,"owner":2874,"repository":2875,"state":2935,"title":2936,"updated_at":2937,"url":2938,"score":2939},"",[2928,2931],{"name":2929,"color":2930},"plugin","887B27",{"name":2932,"color":2933},"documentation","7D625D",1214,"closed","Docs: Plugin list: filter based on tags","2024-12-21T17:45:49Z","https://github.com/woodpecker-ci/woodpecker/issues/1214",0.74885124,{"description":2941,"labels":2942,"number":2944,"owner":2874,"repository":2875,"state":2935,"title":2945,"updated_at":2946,"url":2947,"score":2948},"### Component\n\nweb-ui\n\n### Describe the bug\n\nOn the web ui when you first try to add a secret using the form, It doesn't fill out `events` field in the POST request and gives an 422 (Unprocessable Content). After deselecting and selecting any of the previously selected events (for example just push). It fills out `events` field in the POST request and it succeeds. \r\n\r\n422 response is coming from endpoint `api/repos/:id/secrets`. \r\nRequest payload in the first try: `{\"name\":\"test\",\"value\":\"test\",\"image\":[],\"event\":[\"push\"]}`\r\nRequest payload after deselecting and selecting `tag` event again: `{\"name\":\"test\",\"value\":\"test\",\"image\":[],\"event\":[\"push\"],\"events\":[\"tag\"]}`\r\n\r\nas another note, even though I haven't selected the `push` event, it always sends the field `event` with value of `push`.\n\n### System Info\n\n```shell\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"next-aeb7bcb26a\"}\n```\n\n\n### Additional context\n\n_No response_\n\n### Validations\n\n- [X] Read the [Contributing Guidelines](https://github.com/woodpecker-ci/woodpecker/blob/main/CONTRIBUTING.md).\n- [X] Read the [docs](https://woodpecker-ci.org/docs/intro).\n- [X] Check that there isn't [already an issue](https://github.com/woodpecker-ci/woodpecker/issues) that reports the same bug to avoid creating a duplicate.\n- [X] Checked that the bug isn't fixed in the `next` version already [https://woodpecker-ci.org/faq#which-version-of-woodpecker-should-i-use]\n- [X] Check that this is a concrete bug. For Q&A join our [Discord Chat Server](https://discord.gg/fcMQqSMXJy) or the [Matrix room](https://matrix.to/#/#woodpecker:matrix.org).",[2943],{"name":2868,"color":2869},2896,"Web UI doesn't send correct request to add secrets to the repository","2023-12-01T15:11:59Z","https://github.com/woodpecker-ci/woodpecker/issues/2896",0.7501757,{"description":2950,"labels":2951,"number":2953,"owner":2874,"repository":2875,"state":2935,"title":2954,"updated_at":2955,"url":2956,"score":2957},"### Component\r\n\r\nagent\r\n\r\n### Describe the bug\r\n\r\nWhen having a backend error in the config, i.e. a malformed env var, the step and build are marked as successful even though they should be marked as \"failed\". \r\n\r\n\r\n\r\n\r\nk8s backend\r\n\r\n\r\n### System Info\r\n\r\n```shell\r\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"next-6ab9f802\"}\r\n```\r\n\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Validations\r\n\r\n- [X] Read the [Contributing Guidelines](https://github.com/woodpecker-ci/woodpecker/blob/master/CONTRIBUTING.md).\r\n- [X] Read the [docs](https://woodpecker-ci.org/docs/intro).\r\n- [X] Check that there isn't [already an issue](https://github.com/woodpecker-ci/woodpecker/issues) that reports the same bug to avoid creating a duplicate.\r\n- [X] Checked that the bug isn't fixed in the `next` version already [https://woodpecker-ci.org/faq#which-version-of-woodpecker-should-i-use]\r\n- [X] Check that this is a concrete bug. For Q&A join our [Discord Chat Server](https://discord.gg/fcMQqSMXJy) or the [Matrix room](https://matrix.to/#/#woodpecker:matrix.org).",[2952],{"name":2868,"color":2869},1871,"Build is marked as \"successful\" although a backend error occurred","2025-01-10T21:25:48Z","https://github.com/woodpecker-ci/woodpecker/issues/1871",0.7588951,{"description":2959,"labels":2960,"number":2961,"owner":2874,"repository":2875,"state":2935,"title":2962,"updated_at":2963,"url":2964,"score":2965},"It would be nice if Woodpecker would be able to easily deploy my project like systems like Vercel, Heroku ... do it.\r\n\r\n(Treat this as a general possible outlook into automatic CD with Woodpecker)\r\n\r\n# What I expect in an ideal scenario:\r\n- I can enable a repo (maybe check an auto-mode option)\r\n- It will automatically detect the language, framework etc and build the software\r\n- As Woodpecker is not a hosting platform like Vercel / Heroku on its own, it should use some hosting provider like Hetzner, fly.io, ... and deploy the build artifact directly to it\r\n- It should create one production deployment for my main branch and review deployments for my PRs\r\n\r\n# How this could work:\r\n- Using a plugin which uses [buildpacks](https://buildpacks.io/) to build a repo\r\n- Using a plugin to deploy to a hosting provider\r\n- Maybe some way to auto-generate a wp-config similar to how buildpacks work (liking #1400 and #783 for dynamic config generation)",[],2075,"Automatically deploy repo similar to Vercel / Heroku","2023-08-08T08:05:38Z","https://github.com/woodpecker-ci/woodpecker/issues/2075",0.760045,{"description":2967,"labels":2968,"number":2970,"owner":2874,"repository":2875,"state":2935,"title":2971,"updated_at":2972,"url":2973,"score":2974},"### Component\n\nserver\n\n### Describe the bug\n\nGot this error :\n\n```\nwoodpecker-server | {\"level\":\"info\",\"time\":\"2025-02-13T09:36:51Z\",\"message\":\"log level: info\"}\nwoodpecker-server | {\"level\":\"error\",\"error\":\"can't setup store: could not migrate datastore: migration cron-without-sec failed: attempt to write a readonly database\",\"time\":\"2025-02-13T09:36:51Z\",\"message\":\"error running server\"}\n```\n\n### Steps to reproduce\n\nHave a 2.8.3 with docker compose up\nEdit docker compose to 3.0.0\nUp docker compose\nGot this error\n\n### Expected behavior\n\n_No response_\n\n### System Info\n\n```shell\nClient: Docker Engine - Community\n Version: 27.3.1\n\nDocker Compose version v2.32.4\n```\n\n### Additional context\n\n_No response_\n\n### Validations\n\n- [x] Read the [docs](https://woodpecker-ci.org/docs/intro).\n- [x] Check that there isn't [already an issue](https://github.com/woodpecker-ci/woodpecker/issues) that reports the same bug to avoid creating a duplicate.\n- [x] Checked that the bug isn't fixed in the `next` version already [https://woodpecker-ci.org/versions]",[2969],{"name":2868,"color":2869},4836,"Migration 2.8.3 to 3.0.0 failed - migration cron-without-sec failed","2025-02-13T14:04:04Z","https://github.com/woodpecker-ci/woodpecker/issues/4836",0.7620592,["Reactive",2976],{},["Set"],["ShallowReactive",2979],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fJUtRG3uCTI3dsO69JWw5hrZwcm2qJQ0Hs6fIHM2r5o0":-1},"/woodpecker-ci/woodpecker/2854"]