\n\nAnd here is the outcome on BitBucket:\n\u003Cimg width=\"479\" height=\"182\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/11c2a65d-cbf2-4162-9805-3d035bdac04e\" />\n\n\n### Steps to reproduce\n\n1. Run Woodpecker with BitBucket Cloud forge\n2. Create a pipeline that uses a matrix\n3. Let the pipeline finish on Woodpecker\n4. Observe the build statuses on the commit in BitBucket\n\n### Expected behavior\n\nBoth pipelines should show completed.\n\n### System Info\n\n```shell\nWoodpecker version: v3.8.0\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]",[3207,3210],{"name":3208,"color":3209},"bug","d73a4a",{"name":3211,"color":3212},"forge/bitbucket","E96280",5338,"Build status not completing on matrix pipelines with BitBucket","2025-08-10T17:51:17Z","https://github.com/woodpecker-ci/woodpecker/issues/5338",0.69214565,{"description":3219,"labels":3220,"number":3222,"owner":3143,"repository":3144,"state":3199,"title":3223,"updated_at":3224,"url":3225,"score":3226},"### Component\n\ncli\n\n### Describe the bug\n\nAdding a \"platform\" as suggested in the documentation at https://woodpecker-ci.org/docs/usage/matrix-pipelines#example-matrix-pipeline-using-multiple-platforms throws an\r\n```\r\n❌ Config is invalid\r\nIn (root): Additional property platform is not allowed\r\n```\r\nin `woodpecker lint`.\n\n### System Info\n\n```shell\nwoodpecker-cli version 0.15\r\n\r\nThis is the amd64 Debian package from GitHub releases.\n```\n\n\n### Additional context\n\n```shell\nThe specific section in my file looks like this:\r\n\r\nmatrix:\r\n PLATFORM:\r\n - 'linux/amd64'\r\n - 'linux/arm64'\r\n\r\nplatform: ${PLATFORM}\r\n\r\npipeline:\r\n setup_environment:\r\n(...)\r\n```\n```\n\n\n### Validations\n\n- [X] Read the [Contributing Guidelines](https://github.com/woodpecker-ci/woodpecker/blob/master/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] 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).",[3221],{"name":3208,"color":3209},1056,"\"Additional property platform is not allowed\"","2022-10-11T16:26:56Z","https://github.com/woodpecker-ci/woodpecker/issues/1056",0.7176256,{"description":3228,"labels":3229,"number":3231,"owner":3143,"repository":3144,"state":3199,"title":3232,"updated_at":3233,"url":3234,"score":3235},"### Component\n\nserver\n\n### Describe the bug\n\nWe're running woodpecker on k8s and using postgres for backend / metadata store, this is intermittent issue; sometimes the pipeline works and sometimes we see the error in server logs\r\n\r\n`Getting Error #01: failed to save pipeline for repo; error=\"pq: value too long for type character varying(255)\"`\n\n### Steps to reproduce\n\nNot sure how to re-produce this; since this is very intermittent.\n\n### Expected behavior\n\n_No response_\n\n### System Info\n\n```shell\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"2.6.0\"}\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]",[3230],{"name":3208,"color":3209},4596,"support to allow more than 255 chars for avatar column in 2.x ","2024-12-21T11:06:09Z","https://github.com/woodpecker-ci/woodpecker/issues/4596",0.71855533,{"description":3237,"labels":3238,"number":3240,"owner":3143,"repository":3144,"state":3199,"title":3241,"updated_at":3242,"url":3243,"score":3244},"### Component\n\nserver\n\n### Describe the bug\n\nIn woodpecker v2.3.0, custom yaml files defined in repositories are configured in woodpecker and passed to the external configuration API. This API responds with valid woodpecker workflows based on the custom yaml, allowing this workflow to execute successfully. However, woodpecker 2.4.1 introduces linting on these configured custom yaml files, resulting in failed executions due to linting errors. This change effectively inhibits our ability to upgrade our instance to v2.4.1.\n\n### System Info\n\n```shell\nVersion which works for us\r\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"2.3.0\"}\r\n---\r\nVersion with issue\r\n{\"source\":\"https://github.com/woodpecker-ci/woodpecker\",\"version\":\"2.4.1\"}\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]",[3239],{"name":3208,"color":3209},3536,"Linter errors on repos dependent on external configuration API ","2024-03-22T14:16:02Z","https://github.com/woodpecker-ci/woodpecker/issues/3536",0.7263753,["Reactive",3246],{},["Set"],["ShallowReactive",3249],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fVFjHIaOherB6v_Oe08pVFEpWNWJTC-IHz2_Yw6q37b0":-1},"/woodpecker-ci/woodpecker/5438"]