\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]",[3156,3157],{"name":3140,"color":3141},{"name":3158,"color":3159},"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.78161675,{"description":3166,"labels":3167,"number":3174,"owner":3146,"repository":3147,"state":3148,"title":3175,"updated_at":3176,"url":3177,"score":3178},"and address\r\n- https://github.com/woodpecker-ci/woodpecker/issues/3503 -> #3820\r\n- https://github.com/woodpecker-ci/woodpecker/pull/3733#issuecomment-2180578290\r\n- ...\r\n\r\nTests to run:\r\n- [ ] Run workflow with steps that should only run if the step before [failed,succeded] (could help with questions like: https://github.com/woodpecker-ci/woodpecker/pull/3846#discussion_r1686246455)\r\n- [ ] Services and check if it is started before the steps who need it ...\r\n- [ ] Make sure the Queue respect **labels** and dependencies correctly\r\n- [ ] ...",[3168,3171],{"name":3169,"color":3170},"tests","ACEA1E",{"name":3172,"color":3173},"summary","C3DC73",3819,"Create \"backend integration test\" framework","2024-11-05T23:18:48Z","https://github.com/woodpecker-ci/woodpecker/issues/3819",0.7875404,{"description":3180,"labels":3181,"number":3183,"owner":3146,"repository":3147,"state":3184,"title":3185,"updated_at":3186,"url":3187,"score":3188},"### Component\r\n\r\nserver, web-ui\r\n\r\n### Describe the bug\r\n\r\nHi, I have problem with my woodpecker instance. I'm using Github to provide OAuth2 Authorization. But the problem I cannot log in to the app. When I clicking \"Log in\" button, it returns to the same screen. Sometimes when I do many clicks in small amount time I need reatuhorize it in Github.\r\n\r\nInstance is hidden with ngnix proxy manager. \r\n\r\nMy docker compose looks like this:\r\n```\r\nservices:\r\n woodpecker-server:\r\n image: woodpeckerci/woodpecker-server:latest\r\n expose:\r\n - 8000\r\n - 9000\r\n volumes:\r\n - ./woodpecker-server-data:/var/lib/woodpecker/\r\n environment:\r\n - WOODPECKER_OPEN=false\r\n - WOODPECKER_HOST=${WOODPECKER_HOST}\r\n - WOODPECKER_GITHUB=true\r\n - WOODPECKER_GITHUB_CLIENT=${WOODPECKER_GITHUB_CLIENT}\r\n - WOODPECKER_GITHUB_SECRET=${WOODPECKER_GITHUB_SECRET}\r\n - WOODPECKER_AGENT_SECRET=${WOODPECKER_AGENT_SECRET}\r\n - WOODPECKER_ADMIN=${WOODPECKER_ADMIN}\r\n - WOODPECKER_REPO_OWNERS=${WOODPECKER_REPO_OWNERS}\r\n networks:\r\n - ngnix-internal\r\n - composehook-internal\r\n woodpecker-agent:\r\n image: woodpeckerci/woodpecker-agent:latest\r\n command: agent\r\n restart: always\r\n depends_on:\r\n - woodpecker-server\r\n volumes:\r\n - ./woodpecker-agent-config:/etc/woodpecker\r\n - /var/run/docker.sock:/var/run/docker.sock\r\n environment:\r\n - WOODPECKER_SERVER=woodpecker-server:9000\r\n - WOODPECKER_AGENT_SECRET=${WOODPECKER_AGENT_SECRET}\r\n - WOODPECKER_BACKEND_DOCKER_NETWORK=composehook-internal\r\n networks:\r\n - ngnix-internal\r\n - composehook-internal\r\nnetworks:\r\n ngnix-internal:\r\n external: true\r\n name: ngnix-internal\r\n composehook-internal:\r\n external: true\r\n name: composehook-internal\r\n```\r\n\r\nIn logs I haven't see something weird or wrong.\r\n\r\n\r\n### System Info\r\n\r\n```shell\r\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"2.4.1\"}\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 [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]",[3182],{"name":3140,"color":3141},3689,"closed","Stuck on login screen. ","2024-06-21T08:20:32Z","https://github.com/woodpecker-ci/woodpecker/issues/3689",0.7539142,{"description":3190,"labels":3191,"number":3196,"owner":3146,"repository":3147,"state":3184,"title":3197,"updated_at":3198,"url":3199,"score":3200},"### Component\n\nagent\n\n### Describe the bug\n\nAgent image builds with `next-*` version instead of tag/release. Server version is OK.\n\n### System Info\n\n```shell\n{\"level\":\"info\",\"time\":\"2023-08-17T11:47:41Z\",\"message\":\"Starting Woodpecker server with version '1.0.2'\"}\r\n{\"level\":\"info\",\"time\":\"2023-08-17T12:01:26Z\",\"message\":\"Starting Woodpecker agent with version 'next-d9e06696' and backend 'kubernetes' using platform 'linux/amd64' running up to 1 pipelines in parallel\"}\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).",[3192,3193],{"name":3140,"color":3141},{"name":3194,"color":3195},"build","6AB8BA",2236,"Incorrect version of agent","2023-08-18T14:39:20Z","https://github.com/woodpecker-ci/woodpecker/issues/2236",0.75500816,{"description":3202,"labels":3203,"number":3205,"owner":3146,"repository":3147,"state":3184,"title":3206,"updated_at":3207,"url":3208,"score":3209},"### 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]",[3204],{"name":3140,"color":3141},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.7571351,{"description":3211,"labels":3212,"number":3216,"owner":3146,"repository":3147,"state":3184,"title":3217,"updated_at":3218,"url":3219,"score":3220},"### Component\n\nagent\n\n### Describe the bug\n\nBy default netrc credentials (i.e. git credentials) are not injected into builds unless\r\n\r\n- the repo is set to trusted (which can only be done by admins)\r\n- \"Only inject netrc credentials into trusted containers\" is unchecked\r\n\r\nHowever, the latter does not work as executing a \"git push\" back to the checked out repo does not work when **the option is unchecked**.\r\nIt only works if the repo is set to \"trusted\" - which cannot be enabled by a normal user.\r\n\r\nShowcasing this in an example repo is hard as normal users cannot open the settings of a repo.\r\nI've tested this multiple times in an example repo toggling different options on and off and running a simple `git push` at the end (after a dummy modification).\r\n\r\nAlso I think the current docs are wrong\r\n\r\n> Cloning pipeline step may need git credentials. They are injected via netrc. By default, they're only injected if this option is enabled, the repo is trusted ([see above](#trusted)) or the image is a trusted clone image. If you uncheck the option, git credentials will be injected into any container in clone step.\r\n\r\nI think it should read as:\r\n\r\n\"By default, they're only injected if this option is enabled **and** the repo is trusted - or if the \"inject\" option is unchecked.\"\r\n\r\nAlso \"git credentials will be injected into any container in clone step\" -> should probably be \"into any container **in addition** to the 'clone' step\". \n\n### System Info\n\n```shell\n`next-8629a418f8`\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).",[3213],{"name":3214,"color":3215},"enhancement","7E1FE4",2583,"Injecting netrc credentials into non-trusted containers does not work","2024-11-10T15:42:36Z","https://github.com/woodpecker-ci/woodpecker/issues/2583",0.75741976,{"description":3222,"labels":3223,"number":3230,"owner":3146,"repository":3147,"state":3184,"title":3231,"updated_at":3232,"url":3233,"score":3234},"",[3224,3227],{"name":3225,"color":3226},"plugin","887B27",{"name":3228,"color":3229},"documentation","7D625D",1214,"Docs: Plugin list: filter based on tags","2024-12-21T17:45:49Z","https://github.com/woodpecker-ci/woodpecker/issues/1214",0.7602376,{"description":3236,"labels":3237,"number":3239,"owner":3146,"repository":3147,"state":3184,"title":3240,"updated_at":3241,"url":3242,"score":3243},"### Component\r\n\r\nother\r\n\r\n### Describe the bug\r\n\r\nI am testing version 2.6 in my development environment, so I updated an application code to use \r\n```- evaluate: CI_PIPELINE_DEPLOY_TASK == \"sre-dummy-rest-app\"```\r\ninstead of the 'task:' filter.\r\nIn my github hooks payload I get: \r\n\r\nBut the CI_PIPELINE_DEPLOY_TASK is empty and woodpecker is not running the steps that it should run.\r\n\r\n### Steps to reproduce\r\n\r\nUsing :\r\n``` \r\nwhen:\r\n - evaluate: CI_PIPELINE_DEPLOY_TASK == \"value\" \r\n```\r\n\r\nInstead of:\r\n`task: \"value\"`\r\n\r\n### Expected behavior\r\n\r\nRun with the variable as it should run with the filter in previous versions.\r\n\r\n### System Info\r\n\r\n```shell\r\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"2.6.0\"}\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 [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]",[3238],{"name":3140,"color":3141},3872,"variable CI_PIPELINE_DEPLOY_TASK is empty in woodpecker","2024-07-07T11:43:08Z","https://github.com/woodpecker-ci/woodpecker/issues/3872",0.76881427,{"description":3245,"labels":3246,"number":3248,"owner":3146,"repository":3147,"state":3184,"title":3249,"updated_at":3250,"url":3251,"score":3252},"### Component\n\nagent\n\n### Describe the bug\n\nOn an arm64 agent (Raspberry Pi 4b+), the clone step fails when the container is running in podman:\r\n\r\n```\r\n+ git init -b main\r\nInitialized empty Git repository in /woodpecker/src/git.vdx.hu/voidcontext/nix-config/.git/\r\n+ git config --global --replace-all safe.directory /woodpecker/src/git.vdx.hu/voidcontext/nix-config\r\n+ git remote add origin https://git.vdx.hu/voidcontext/nix-config.git\r\n+ git fetch --no-tags --depth=1 --filter=tree:0 origin +a4b83a869d6366bf24921b8f4f3f5836f806f57e:fatal: unable to access 'https://git.vdx.hu/voidcontext/nix-config.git/': Could not resolve host: git.vdx.hu\r\nexit status 128\r\n```\r\n\r\nThe server is on a different server (on amd64).\r\n\r\nExample: https://woodpecker.ci.vdx.hu/repos/109/pipeline/119/5\r\n\r\nThe same pipeline is successful on an amd64 agent (Kubernetes on a 3rd machine).\r\n\r\nThe issue seems to be similar to https://github.com/woodpecker-ci/woodpecker/issues/1407 which has been closed bacause of inactivity.\n\n### Steps to reproduce\n\n1) install server on amd64 machine (A)\r\n2) install agent on arm64 machine (B) using Docker backend that points to a docker compatible podman socket.\r\n3) Run pipeline\n\n### Expected behavior\n\nGit is able to resolve the host as it has a public DNS record.\n\n### System Info\n\n```shell\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"2.6.0\"}\r\n```\n```\n\n\n### Additional context\n\nUnfortunately I wasn't able to test this on `next`.\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]",[3247],{"name":3140,"color":3141},3892,"Git clone step fails with \"Could not resolve host\" error when running fetch","2024-07-18T22:49:20Z","https://github.com/woodpecker-ci/woodpecker/issues/3892",0.76899016,["Reactive",3254],{},["Set"],["ShallowReactive",3257],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f9g8f_8isP02SDOIGMyYl0SUvy_tSS_8PR56KtaQh9tM":-1},"/woodpecker-ci/woodpecker/5045"]