\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]",[2882,2885],{"name":2883,"color":2884},"bug","d73a4a",{"name":2886,"color":2887},"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.7690606,{"description":2894,"labels":2895,"number":2897,"owner":2872,"repository":2873,"state":2874,"title":2898,"updated_at":2899,"url":2900,"score":2901},"### Component\n\nserver\n\n### Describe the bug\n\nWhen adding a global registry, if you add the protocol (ie https://), the entry is not removable via the UI.\n\n### Steps to reproduce\n\ncreate two global registry records, mytest.local, and https://mytest.local.\r\n\r\nmytest.local will be removable.\r\nhttps://mytest.local will say it's being removed, but will persist.\n\n### Expected behavior\n\nBoth records should be removed.\n\n### System Info\n\n```shell\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"2.7.3\"}\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]",[2896],{"name":2883,"color":2884},4348,"Poorly formatted global registry can not be deleted.","2024-12-14T07:57:22Z","https://github.com/woodpecker-ci/woodpecker/issues/4348",0.7784476,{"description":2903,"labels":2904,"number":2912,"owner":2872,"repository":2873,"state":2913,"title":2914,"updated_at":2915,"url":2916,"score":2917},"### Component\r\n\r\nserver\r\n\r\n### Describe the bug\r\n\r\nAfter upgrading the server from `v0.15` to `v1.0` woodpecker only returns 404 and the following entries are continuously written to the log output\r\n\r\n```\r\n{\r\n \"level\":\"fatal\",\r\n \"error\":\"error to create migrations table: pq: relation \\\"UQE_migrations_name\\\" already exists\",\r\n \"time\":\"2023-07-26T22:49:03Z\",\r\n \"message\":\"could not migrate datastore\"\r\n}\r\n```\r\n\r\nNo other changes were made besides the update of the docker image.\r\n\r\n### System Info\r\n\r\n```shell\r\n- docker-compose version - 1.29.2\r\n- Docker Engine version - 23.0.5\r\n\r\nContainers:\r\n- docker.io/woodpeckerci/woodpecker-server:v1.0\r\n- registry.developers.crunchydata.com/crunchydata/crunchy-postgres:ubi8-14.6-2 (PG-14)\r\n\r\nENV Settings:\r\n\r\nWOODPECKER_OPEN=True\r\nWOODPECKER_SERVER_ADDR=0.0.0.0:8000\r\nWOODPECKER_GRPC_ADDR=0.0.0.0:9000\r\nWOODPECKER_ADMIN=admin\r\nWOODPECKER_DOCKER_CONFIG=\r\nWOODPECKER_LOG_LEVEL=info\r\nWOODPECKER_HOST=https://woodpecker.my.tld\r\nWOODPECKER_SESSION_EXPIRES=24h\r\nWOODPECKER_AGENT_SECRET=xxxxxx\r\nWOODPECKER_DATABASE_DRIVER=postgres\r\nWOODPECKER_DATABASE_DATASOURCE=postgres://xxxxxx:xxxxxx@db/woodpecker?sslmode=disable&application_name=woodpecker\r\nWOODPECKER_GITEA=True\r\nWOODPECKER_GITEA_URL=https://forgejo.my.tld\r\nWOODPECKER_GITEA_CLIENT=xxxxxx\r\nWOODPECKER_GITEA_SECRET=xxxxxx\r\n```\r\n\r\n\r\n### Additional context\r\n\r\ntrace log:\r\n```\r\n{\r\n \"time\":\"2023-07-26T23:22:17Z\",\r\n \"caller\":\"/woodpecker/src/github.com/woodpecker-ci/woodpecker/cmd/server/server.go:82\",\r\n \"message\":\"LogLevel = trace\"\r\n}\r\n{\r\n \"level\":\"trace\",\r\n \"time\":\"2023-07-26T23:22:17Z\",\r\n \"caller\":\"/woodpecker/src/github.com/woodpecker-ci/woodpecker/cmd/server/setup.go:232\",\r\n \"message\":\"Forge (gitea) opts: gitea.Opts{URL:\\\"https://forgejo.my.tld\\\", Client:\\\"xxxxxx\\\", Secret:\\\"xxxxxx\\\", SkipVerify:false}\"\r\n}\r\n{\r\n \"level\":\"trace\",\r\n \"time\":\"2023-07-26T23:22:17Z\",\r\n \"caller\":\"/woodpecker/src/github.com/woodpecker-ci/woodpecker/cmd/server/setup.go:87\",\r\n \"message\":\"setup datastore: store.Opts{Driver:\\\"postgres\\\", Config:\\\"postgres://xxxxxx:xxxxxx@db/woodpecker?sslmode=disable&application_name=woodpecker\\\", XORM:store.XORM{Log:false, ShowSQL:false}}\"\r\n}\r\n{\r\n \"level\":\"fatal\",\r\n \"error\":\"error to create migrations table: pq: relation \\\"UQE_migrations_name\\\" already exists\",\r\n \"time\":\"2023-07-26T23:22:17Z\",\r\n \"caller\":\"/woodpecker/src/github.com/woodpecker-ci/woodpecker/cmd/server/setup.go:94\",\r\n \"message\":\"could not migrate datastore\"\r\n}\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).\r\n\r\n----\r\n*upstream issue: https://gitea.com/xorm/xorm/issues/2317*",[2905,2906,2909],{"name":2883,"color":2884},{"name":2907,"color":2908},"server","5D7A92",{"name":2910,"color":2911},"dependencies","006b75",2038,"closed","pq: relation \"UQE_migrations_name\" already exists","2023-12-19T02:30:47Z","https://github.com/woodpecker-ci/woodpecker/issues/2038",0.7388458,{"description":2919,"labels":2920,"number":2925,"owner":2872,"repository":2873,"state":2913,"title":2926,"updated_at":2927,"url":2928,"score":2929},"### Component\n\nserver\n\n### Describe the bug\n\nWhen specifying clone path relative to workspace behavior has broken in latest `next` version and does not work as it would be expected.\n\nMost probably broken by #5023\n\nWorks fine downgrading to v3.4.0\n\n### Steps to reproduce\n\nExample pipeline:\n```yaml\nclone:\n - name: clone\n image: woodpeckerci/plugin-git:2.6.2\n\n - name: clone-other\n image: woodpeckerci/plugin-git:2.6.2\n settings:\n remote: https://github.com/lafriks/test.git\n path: relative/path/other\n ref: ${CI_COMMIT_REF}\n depth: 1\n\nsteps:\n - name: test\n image: alpine:latest\n commands:\n - ls -la .\n```\n\n### Expected behavior\n\nTo clone main repo and other repo in subdirectory `relative/path/other`\n\n### System Info\n\n```shell\nnext\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]",[2921,2922],{"name":2883,"color":2884},{"name":2923,"color":2924},"backend/docker","bfdadc",5045,"Broken clone path directory","2025-04-02T07:21:27Z","https://github.com/woodpecker-ci/woodpecker/issues/5045",0.7453483,{"description":2931,"labels":2932,"number":2934,"owner":2872,"repository":2873,"state":2913,"title":2935,"updated_at":2936,"url":2937,"score":2938},"### 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]",[2933],{"name":2883,"color":2884},3689,"Stuck on login screen. ","2024-06-21T08:20:32Z","https://github.com/woodpecker-ci/woodpecker/issues/3689",0.74604106,{"description":2940,"labels":2941,"number":2946,"owner":2872,"repository":2873,"state":2913,"title":2947,"updated_at":2948,"url":2949,"score":2950},"### 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).",[2942,2943],{"name":2883,"color":2884},{"name":2944,"color":2945},"build","6AB8BA",2236,"Incorrect version of agent","2023-08-18T14:39:20Z","https://github.com/woodpecker-ci/woodpecker/issues/2236",0.74992675,{"description":2952,"labels":2953,"number":2955,"owner":2872,"repository":2873,"state":2913,"title":2956,"updated_at":2957,"url":2958,"score":2959},"### Component\r\n\r\nother\r\n\r\n### Describe the bug\r\n\r\nEnhance pipeline list https://github.com/woodpecker-ci/woodpecker/pull/3898 was reverted before release.\r\n\r\n### Steps to reproduce\r\n\r\n1. Go to [Releases](https://github.com/woodpecker-ci/woodpecker/releases) page\r\n2. and see #3898 is mentioned as enhancement, there is no #3926\r\n\r\n### Expected behavior\r\n\r\nThere should not be #3898 in release notes.\r\n\r\n### System Info\r\n\r\nRelated to 2.7.0\r\n\r\n\r\n### Additional context\r\n\r\nhttps://github.com/woodpecker-ci/woodpecker/pull/3926\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]",[2954],{"name":2883,"color":2884},3998,"Remove 3898 from release notes","2024-08-04T23:34:14Z","https://github.com/woodpecker-ci/woodpecker/issues/3998",0.75463283,{"description":2961,"labels":2962,"number":2964,"owner":2872,"repository":2873,"state":2913,"title":2965,"updated_at":2966,"url":2967,"score":2968},"### Component\r\n\r\nweb-ui\r\n\r\n### Describe the bug\r\n\r\nThe code contains the inline styles.\r\nInline style, seems, was only in `web/src/components/admin/settings/queue/AdminQueueStats.vue:25` before.\r\n\r\n### Expected behavior\r\n\r\nShould not be inline styles.\r\n\r\nhttps://developer.mozilla.org/en-US/docs/Web/HTML/Global_attributes/style\r\nhttps://stackoverflow.com/questions/2612483/whats-so-bad-about-in-line-css\r\nhttps://content-security-policy.com/unsafe-inline/\r\n\r\n### System Info\r\n\r\n`next`\r\n\r\n### Additional context\r\n\r\nI accidentally saw #4609 and wanted to comment there, but I'm not allowed to comment on `pat-s` issues and PRs.\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]",[2963],{"name":2883,"color":2884},4616,"Inline styles","2024-12-27T23:10:03Z","https://github.com/woodpecker-ci/woodpecker/issues/4616",0.76168275,{"description":2970,"labels":2971,"number":2973,"owner":2872,"repository":2873,"state":2913,"title":2974,"updated_at":2975,"url":2976,"score":2977},"### 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).",[2972],{"name":2883,"color":2884},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.76601243,["Reactive",2979],{},["Set"],["ShallowReactive",2982],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f-KfaXUT2FUnHsPpb5hMBtOeqfLEBeIaR_tHn1TUsNtY":-1},"/woodpecker-ci/woodpecker/2583"]