{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":10148417,"defaultBranch":"main","name":"styleguide","ownerLogin":"TYPO3-CMS","currentUserCanPush":false,"isFork":false,"isEmpty":false,"createdAt":"2013-05-18T23:22:01.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/3920091?v=4","public":true,"private":false,"isOrgOwned":true},"refInfo":{"name":"","listCacheKey":"v0:1715675912.0","currentOid":""},"activityList":{"items":[{"before":"8c10fb17cd62007aa0ae6c18886db707edd6afeb","after":"7f4d34415a9c7e470b862273dde092d9675126ab","ref":"refs/heads/main","pushedAt":"2024-06-11T13:12:09.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"TYPO3IncTeam","name":"TYPO3 GmbH","path":"/TYPO3IncTeam","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20440329?s=80&v=4"},"commit":{"message":"[TASK] Remove \"Access for 'admin' users only!\" hints in About module\n\nThe \"About\" module lists, among other things, all backend modules\navailable in the system. If an admin or editor does not have access to\na module, it will not be displayed in the \"About\" module list.\n\nSome of the modules listed contained a note that the module was only\naccessible to administrators. With the introduction of the system\nmaintainer role, this note is no longer applicable. In addition, this\nnote was missing for some modules that cannot be made accessible to the\neditor at all (e.g. \"Access\" module).\n\nIf an admin/system maintainer wants to check which backend modules an\neditor can access, he usually switches to the backend user (via the\n\"Backend Users\" backend module). Calling the \"About\" module is not\nsufficient at this point, as settings in backend user groups and the\nbackend user accounts themselves also influence whether a backend user\ncan access a backend module or not.\n\nFor this reason, this note in the \"About\" module is now being removed.\n\nResolves: #104040\nReleases: main, 12.4\nChange-Id: Ib27581a9f1fc48985d42550622caffcf0615a0d4\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84610\nReviewed-by: Michael Telgkamp \nTested-by: core-ci \nReviewed-by: Jasmina Ließmann \nReviewed-by: Georg Ringer \nTested-by: Georg Ringer \nTested-by: Michael Telgkamp \nTested-by: Jasmina Ließmann ","shortMessageHtmlLink":"[TASK] Remove \"Access for 'admin' users only!\" hints in About module"}},{"before":"8cfab4d1a33515a3b6c22a0a186a2445ba04afd5","after":"8c10fb17cd62007aa0ae6c18886db707edd6afeb","ref":"refs/heads/main","pushedAt":"2024-06-11T09:33:05.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"TYPO3IncTeam","name":"TYPO3 GmbH","path":"/TYPO3IncTeam","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20440329?s=80&v=4"},"commit":{"message":"[TASK] Add streamlined progress bar component\n\nThis commit introduces a new component to render progress bars in a\nstreamlined fashion, addressing common accessibility issues by\nproviding proper aria attributes.\n\nThe component supports a `max` value and a relative `value` attribute.\nIf `value` is omitted, the progress bar is rendered in an indeterminate\nstate.\nIf `value` is present, an optional `severity` attribute can get passed\nto visually describe the state of the progress bar. Please note that\nonly successful, warning and error states are supported.\nAdditionally, an optional `label` can get passed, describing the\nprogress bar and its current state.\n\nImportant note: this component is rather experimental by now and may\nchange in a few details. Until further notice, this component is\nstrictly for internal use only.\n\nResolves: #103767\nReleases: main\nChange-Id: I2a99c10e589482a2972935f49af87119ea899f34\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84038\nTested-by: core-ci \nTested-by: Benjamin Franzke \nTested-by: Georg Ringer \nReviewed-by: Georg Ringer \nReviewed-by: Andreas Nedbal \nTested-by: Andreas Nedbal \nReviewed-by: Benjamin Franzke ","shortMessageHtmlLink":"[TASK] Add streamlined progress bar component"}},{"before":"f9aa5c2593f79a66cb7f60c4f8febf1288899199","after":"26c2c24f7f00e14fcb11acfcf1a1d22716145e4a","ref":"refs/heads/13.1","pushedAt":"2024-05-14T09:11:28.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"TYPO3IncTeam","name":"TYPO3 GmbH","path":"/TYPO3IncTeam","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20440329?s=80&v=4"},"commit":{"message":"[TASK] Set TYPO3 version to 13.1.2-dev\n\nChange-Id: Ibb198fb5282ca533bfcc9c099cf4f119587144b6\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84273\nReviewed-by: Oliver Hader \nTested-by: core-ci \nTested-by: Oliver Hader ","shortMessageHtmlLink":"[TASK] Set TYPO3 version to 13.1.2-dev"}},{"before":"6ffe968df389c236c48ed41cc241f8d6655ae52f","after":"f9aa5c2593f79a66cb7f60c4f8febf1288899199","ref":"refs/heads/13.1","pushedAt":"2024-05-14T08:35:11.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"TYPO3IncTeam","name":"TYPO3 GmbH","path":"/TYPO3IncTeam","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20440329?s=80&v=4"},"commit":{"message":"[RELEASE] Release of TYPO3 13.1.1\n\nChange-Id: I01652247e7d563d1ac6061428a62f46a312e77d4\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84272\nReviewed-by: Oliver Hader \nTested-by: Oliver Hader ","shortMessageHtmlLink":"[RELEASE] Release of TYPO3 13.1.1"}},{"before":"ffedb2fc7a2f7957b1577ac3580d29bc71ac41aa","after":"6ffe968df389c236c48ed41cc241f8d6655ae52f","ref":"refs/heads/13.1","pushedAt":"2024-05-13T09:00:37.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"TYPO3IncTeam","name":"TYPO3 GmbH","path":"/TYPO3IncTeam","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20440329?s=80&v=4"},"commit":{"message":"[TASK] Set TYPO3 version to 13.1.1-dev\n\nChange-Id: Ie9d120d9008d777d870b9a71c76aad17b57d71de\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84219\nTested-by: core-ci \nTested-by: Stefan Bürk \nReviewed-by: Stefan Bürk \nReviewed-by: Benjamin Franzke \nReviewed-by: Oliver Hader \nTested-by: Benjamin Franzke \nTested-by: Oliver Hader \nReviewed-by: Jörg Bösche ","shortMessageHtmlLink":"[TASK] Set TYPO3 version to 13.1.1-dev"}},{"before":null,"after":"ffedb2fc7a2f7957b1577ac3580d29bc71ac41aa","ref":"refs/heads/13.1","pushedAt":"2024-05-13T08:14:56.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"TYPO3IncTeam","name":"TYPO3 GmbH","path":"/TYPO3IncTeam","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20440329?s=80&v=4"},"commit":{"message":"[RELEASE] Release of TYPO3 13.1.0\n\nChange-Id: I0de3c394a9e37ca840c3d0aa6f6df745bca8ac3b\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83992\nTested-by: Benni Mack \nReviewed-by: Benni Mack ","shortMessageHtmlLink":"[RELEASE] Release of TYPO3 13.1.0"}},{"before":"48cb6cb1a0d644e729e2ae66cb6206965e4ac877","after":"8cfab4d1a33515a3b6c22a0a186a2445ba04afd5","ref":"refs/heads/main","pushedAt":"2024-05-08T09:01:37.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"TYPO3IncTeam","name":"TYPO3 GmbH","path":"/TYPO3IncTeam","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20440329?s=80&v=4"},"commit":{"message":"[BUGFIX] Fix positioning of containers in EXT:styleguide BE module\n\nThe containers used in the backend module of EXT:styleguide are now\nbased on flex boxes and don't use absolute positioning anymore. This\nenabled the possibility to scroll when the navigation needs more space\nthan the actual content and also fixes positioning in right-to-left\nscenarios.\n\nResolves: #103794\nReleases: main\nChange-Id: Ie3fcbf7f7141bf16749dc66b45e185168e469260\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84147\nReviewed-by: Andreas Kienast \nTested-by: Frank Nägler \nReviewed-by: Benjamin Franzke \nTested-by: core-ci \nTested-by: Andreas Kienast \nTested-by: Benjamin Franzke \nReviewed-by: Frank Nägler ","shortMessageHtmlLink":"[BUGFIX] Fix positioning of containers in EXT:styleguide BE module"}},{"before":"3edbd282ac68fe9e98256ec13c122684b1509731","after":"48cb6cb1a0d644e729e2ae66cb6206965e4ac877","ref":"refs/heads/main","pushedAt":"2024-04-30T09:15:29.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"TYPO3IncTeam","name":"TYPO3 GmbH","path":"/TYPO3IncTeam","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20440329?s=80&v=4"},"commit":{"message":"[TASK] Use PAGEVIEW in EXT:styleguide site set\n\nThe EXT:styleguide extension currently\nprovides two ways of frontend rendering.\nThe \"old\" way using a `sys_template`\nrecord and the \"new\" way, using site sets.\n\nTo not only test the new site sets feature,\nbut also the new PAGEVIEW cObject is the\ncorresponding TypoScript now using the\nPAGEVIEW for page rendering.\n\nThis one hand is the best practice and on\nthe other hand also allows to test both\nways: FLUIDTEMPLATE and PAGEVIEW in one\nextension.\n\nRequired structural changes also showcase\nwhat has to be done when migrating extensions\nto site sets and PAGEVIEW.\n\nResolves: #103733\nReleases: main\nChange-Id: I71bb28a6e6d39b1232d5283e548044b421d3b5c9\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84037\nReviewed-by: Benni Mack \nReviewed-by: Benjamin Franzke \nTested-by: Benni Mack \nReviewed-by: Jörg Bösche \nTested-by: core-ci \nTested-by: Benjamin Franzke ","shortMessageHtmlLink":"[TASK] Use PAGEVIEW in EXT:styleguide site set"}},{"before":"f11ebbd6e4b6544653fdc46e638f14aca0ea6ab0","after":"3edbd282ac68fe9e98256ec13c122684b1509731","ref":"refs/heads/main","pushedAt":"2024-04-26T08:04:02.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"TYPO3IncTeam","name":"TYPO3 GmbH","path":"/TYPO3IncTeam","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20440329?s=80&v=4"},"commit":{"message":"[BUGFIX] Respect option 'with site set' for ext:styleguide generator\n\nWith #103523 site sets for ext:styleguide were introduced and\nthe page tree generator received an option to create a frontend\ndemo section using the shipped set.\n\nNow the click on this button will actually respect the user's wish\nand create the site using the set and not create a sys_template\nrecord.\n\nResolves: #103732\nRelated: #103523\nReleases: main\nChange-Id: I1560150c24f643a9ac1b7aefe3d7b0fbe109d62e\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84034\nReviewed-by: Andreas Kienast \nTested-by: Andreas Kienast \nTested-by: Benjamin Franzke \nReviewed-by: Benjamin Franzke \nTested-by: core-ci ","shortMessageHtmlLink":"[BUGFIX] Respect option 'with site set' for ext:styleguide generator"}},{"before":"811a2ca93e5888ccf5b2e7e33ab22e532834cc5b","after":"f11ebbd6e4b6544653fdc46e638f14aca0ea6ab0","ref":"refs/heads/main","pushedAt":"2024-04-26T07:21:05.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"TYPO3IncTeam","name":"TYPO3 GmbH","path":"/TYPO3IncTeam","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20440329?s=80&v=4"},"commit":{"message":"[TASK] Streamline Shadows\n\nWe're enhancing our backend by introducing a refined system for shadows.\nThe default and strong shadows remain for simple components, while\ntooltips, flyouts, dialogs, and windows have dedicated ones.\n\nThis streamlines shadow definitions across elements, ensuring\nconsistency. Shadows support both light and dark modes for visibility\nacross all settings.\n\nResolves: #103726\nReleases: main\nChange-Id: Id02122a9f48833df03e28613642499b63c339b45\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84019\nTested-by: Benjamin Franzke \nReviewed-by: Benjamin Franzke \nReviewed-by: Benjamin Kott \nTested-by: Andreas Kienast \nTested-by: Benjamin Kott \nReviewed-by: Andreas Kienast \nTested-by: core-ci ","shortMessageHtmlLink":"[TASK] Streamline Shadows"}},{"before":"095a0979c9b6ac9fe4f2254e51dfc34313d3956a","after":"811a2ca93e5888ccf5b2e7e33ab22e532834cc5b","ref":"refs/heads/main","pushedAt":"2024-04-26T07:11:45.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"TYPO3IncTeam","name":"TYPO3 GmbH","path":"/TYPO3IncTeam","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20440329?s=80&v=4"},"commit":{"message":"[TASK] Use site sets in EXT:styleguide\n\nProvide a new (default) EXT:styleguide frontend\ngenerator that uses site set infrastructure\nprovided by #103437, #103439 and #103522.\n\nThe old sys_template-root based renderer is\npreserved and tested independently\n\nResolves: #103034\nRelated: #103437\nRelated: #103439\nRelated: #103522\nReleases: main\nChange-Id: I53c986d7a47c8c2687b2a240410f9d4130fbae4b\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83696\nTested-by: core-ci \nTested-by: Benjamin Franzke \nTested-by: Benni Mack \nReviewed-by: Benni Mack \nTested-by: Stefan Bürk \nReviewed-by: Stefan Bürk \nReviewed-by: Benjamin Franzke ","shortMessageHtmlLink":"[TASK] Use site sets in EXT:styleguide"}},{"before":"ffedb2fc7a2f7957b1577ac3580d29bc71ac41aa","after":"095a0979c9b6ac9fe4f2254e51dfc34313d3956a","ref":"refs/heads/main","pushedAt":"2024-04-23T07:36:32.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"TYPO3IncTeam","name":"TYPO3 GmbH","path":"/TYPO3IncTeam","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20440329?s=80&v=4"},"commit":{"message":"[TASK] Set TYPO3 version to 13.2.0-dev\n\nChange-Id: I06f3088f1b06adc56000391ea0af8bc199586cb8\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83993\nTested-by: core-ci \nTested-by: Benni Mack \nReviewed-by: Benni Mack ","shortMessageHtmlLink":"[TASK] Set TYPO3 version to 13.2.0-dev"}},{"before":"0e359926b3784cce6fa2e722e18e32221f746cc3","after":"ffedb2fc7a2f7957b1577ac3580d29bc71ac41aa","ref":"refs/heads/main","pushedAt":"2024-04-23T07:12:29.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"TYPO3IncTeam","name":"TYPO3 GmbH","path":"/TYPO3IncTeam","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20440329?s=80&v=4"},"commit":{"message":"[RELEASE] Release of TYPO3 13.1.0\n\nChange-Id: I0de3c394a9e37ca840c3d0aa6f6df745bca8ac3b\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83992\nTested-by: Benni Mack \nReviewed-by: Benni Mack ","shortMessageHtmlLink":"[RELEASE] Release of TYPO3 13.1.0"}},{"before":"f6d4b51fd40ad799a6a56c17c68b8694244ac41e","after":"0e359926b3784cce6fa2e722e18e32221f746cc3","ref":"refs/heads/main","pushedAt":"2024-04-02T20:31:09.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"TYPO3IncTeam","name":"TYPO3 GmbH","path":"/TYPO3IncTeam","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20440329?s=80&v=4"},"commit":{"message":"[BUGFIX] Bring back valuePicker for TCA type `email`\n\nWhile extracting dedicated TCA types from the god type `input`, the\n`valuePicker` option was forgotten for type `email`. Other types like\n`number` do have this option.\n\nAn acceptance test is added to ensure this option will not be dropped\nby accident in the future.\n\nResolves: #103510\nRelated: #97013\nReleases: main, 12.4\nChange-Id: I95c51d858ca9cb3caefa174cd8ce5946c8352aa2\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83631\nReviewed-by: Georg Ringer \nReviewed-by: Benni Mack \nTested-by: core-ci \nTested-by: Benni Mack \nTested-by: Georg Ringer \nTested-by: Nikita Hovratov \nReviewed-by: Nikita Hovratov ","shortMessageHtmlLink":"[BUGFIX] Bring back valuePicker for TCA type email"}},{"before":"97bd529cd87ae6667bdf8d425211e540c87aadbc","after":"f6d4b51fd40ad799a6a56c17c68b8694244ac41e","ref":"refs/heads/main","pushedAt":"2024-03-29T09:50:08.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"TYPO3IncTeam","name":"TYPO3 GmbH","path":"/TYPO3IncTeam","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20440329?s=80&v=4"},"commit":{"message":"[TASK] Extract site persistence into separate service\n\nThe SiteConfiguration service is currently needed during installation\nphase for writing site configurations. This limits symfony dependency\ninjection usage and basically requires that all services needed by\nSiteConfiguration need to be defined and manually wired in\nServiceProvider php code.\n\nThe writing part is now split into a separate service that can be used\nin EXT:install SetupService as before.\n\nResolves: #103450\nReleases: main\nChange-Id: I9cb579ade537c794ce7c1a844b3d7bec7c1b653e\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83557\nTested-by: core-ci \nReviewed-by: Jörg Bösche \nReviewed-by: Georg Ringer \nTested-by: Georg Ringer \nTested-by: Benni Mack \nReviewed-by: Benni Mack ","shortMessageHtmlLink":"[TASK] Extract site persistence into separate service"}},{"before":"192c819bdbbca84b0fde4993f7160aee3855a6a3","after":"cb1c1305043dfd64effe692c6caceae416e82930","ref":"refs/heads/11","pushedAt":"2024-03-13T07:50:21.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"lolli42","name":"Christian Kuhn","path":"/lolli42","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/2178068?s=80&v=4"},"commit":{"message":"[RELEASE] 11.5.5 Minor fixes","shortMessageHtmlLink":"[RELEASE] 11.5.5 Minor fixes"}},{"before":"4e508160839ee04ff81167e596f0aa8eb68f9028","after":"dfb2cd72d8b78dbb7ed7ca7f27dedd1352bc377a","ref":"refs/heads/12","pushedAt":"2024-03-13T07:40:46.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"lolli42","name":"Christian Kuhn","path":"/lolli42","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/2178068?s=80&v=4"},"commit":{"message":"[RELEASE] 12.0.5 Minor fixes","shortMessageHtmlLink":"[RELEASE] 12.0.5 Minor fixes"}},{"before":"c086e2749b9ab2a2effa39d3e2c5b19b354fe892","after":"192c819bdbbca84b0fde4993f7160aee3855a6a3","ref":"refs/heads/11","pushedAt":"2024-03-13T07:29:00.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"lolli42","name":"Christian Kuhn","path":"/lolli42","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/2178068?s=80&v=4"},"commit":{"message":"[TASK] Clean up usages of typo3conf/ext/styleguide (#479)\n\nSome left over usages pointing to\r\ntypo3conf/ext/styleguide directly.\r\n\r\nThis is a backport for v12 compose-mode compatibility where\r\nfiles need to be referenced via API for path resolution\r\nto work (to use /_assets/… instead of a static path pointing\r\nto /typo3conf/).\r\n\r\nResolves: #102235\r\nReleases: main, 12, 11\r\nUpstream: https://review.typo3.org/c/Packages/TYPO3.CMS/+/81649\r\n\r\nCo-authored-by: Christian Kuhn ","shortMessageHtmlLink":"[TASK] Clean up usages of typo3conf/ext/styleguide (#479)"}},{"before":"170f06dff0c7af136cb0912c15d77795da4bcedc","after":"4e508160839ee04ff81167e596f0aa8eb68f9028","ref":"refs/heads/12","pushedAt":"2024-03-13T07:28:42.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"lolli42","name":"Christian Kuhn","path":"/lolli42","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/2178068?s=80&v=4"},"commit":{"message":"[TASK] Clean up usages of typo3conf/ext/styleguide (#478)\n\nSome left over usages pointing to\r\ntypo3conf/ext/styleguide directly.\r\n\r\nThis is a backport for v12 compose-mode compatibility where\r\nfiles need to be referenced via API for path resolution\r\nto work (to use /_assets/… instead of a static path pointing\r\nto /typo3conf/).\r\n\r\nResolves: #102235\r\nReleases: main, 12, 11\r\nUpstream: https://review.typo3.org/c/Packages/TYPO3.CMS/+/81649\r\n\r\nCo-authored-by: Christian Kuhn ","shortMessageHtmlLink":"[TASK] Clean up usages of typo3conf/ext/styleguide (#478)"}},{"before":"d2a6d60c2e0316bea366a0ab56fa9e26f5f10c3b","after":"97bd529cd87ae6667bdf8d425211e540c87aadbc","ref":"refs/heads/main","pushedAt":"2024-03-08T18:18:27.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"TYPO3IncTeam","name":"TYPO3 GmbH","path":"/TYPO3IncTeam","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20440329?s=80&v=4"},"commit":{"message":"[TASK] Use TypoScript static file dependency chain in EXT:styleguide\n\nLoad TypoScript dependencies via include_static_file.txt which\nis the defined pattern for loading dependencies of a static template,\nensuring that both constants and typoscript setup of dependencies are\nloaded, without having to load all required dependencies both in\nconstants.typoscript and setup.typoscript.\n\nReleases: main\nResolves: #103278\nChange-Id: I5bd007b15ca410d704ae1347c3ec90c7fdf7a4d4\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83124\nReviewed-by: Stefan Bürk \nTested-by: Benni Mack \nReviewed-by: Benni Mack \nTested-by: Stefan Bürk \nTested-by: core-ci ","shortMessageHtmlLink":"[TASK] Use TypoScript static file dependency chain in EXT:styleguide"}},{"before":"d79d9b2ff5d20078b48f1a236bc0fa0c3be84ce8","after":"d2a6d60c2e0316bea366a0ab56fa9e26f5f10c3b","ref":"refs/heads/main","pushedAt":"2024-03-08T16:59:21.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"TYPO3IncTeam","name":"TYPO3 GmbH","path":"/TYPO3IncTeam","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20440329?s=80&v=4"},"commit":{"message":"[DOCS] Switch styleguide documentation to PHP-based rendering\n\n* Introduce a guides.xml, the presence of this file\n triggers the new rendering.\n* Remove outdated genindex: not supported anymore\n* Remove old Settings.cfg, was only used for Sphinx\n\nAttention: Backport needs manual changes to the guides.xml.\n\nResolves: #103341\nReleases: main\nChange-Id: Ie7eea104f996882b07017e6965a95cd8aa966a5f\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83353\nTested-by: core-ci \nTested-by: Lina Wolf <112@linawolf.de>\nReviewed-by: Lina Wolf <112@linawolf.de>\nReviewed-by: Chris Müller \nTested-by: Chris Müller ","shortMessageHtmlLink":"[DOCS] Switch styleguide documentation to PHP-based rendering"}},{"before":"faf71408271d1a60dc80b6fb91b54c7f239a3ead","after":"d79d9b2ff5d20078b48f1a236bc0fa0c3be84ce8","ref":"refs/heads/main","pushedAt":"2024-02-28T14:27:38.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"TYPO3IncTeam","name":"TYPO3 GmbH","path":"/TYPO3IncTeam","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20440329?s=80&v=4"},"commit":{"message":"[BUGFIX] Remove invalid flex form configuration\n\nSince #102970, it's no longer possible to use\nDB relations in nested types for flex forms.\n\nA forgotten TCA configuration in\n`tx_styleguide_elements_folder` is removed\naccordingly.\n\nResolves: #103227\nRelated: #102970\nReleases: main\nChange-Id: I06c6a5953fa9dca1e8a90b677c3c890580da8b6b\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83159\nReviewed-by: Stefan Bürk \nTested-by: Christian Kuhn \nReviewed-by: Christian Kuhn \nTested-by: core-ci \nTested-by: Stefan Bürk ","shortMessageHtmlLink":"[BUGFIX] Remove invalid flex form configuration"}},{"before":"664c50e88ae1da6455444b56bd8e42c550749780","after":"faf71408271d1a60dc80b6fb91b54c7f239a3ead","ref":"refs/heads/main","pushedAt":"2024-02-23T13:54:41.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"TYPO3IncTeam","name":"TYPO3 GmbH","path":"/TYPO3IncTeam","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20440329?s=80&v=4"},"commit":{"message":"[TASK] Use phpunit attributes over annotations\n\nphpunit 11 deprecates annotations like `@test` and\n`@dataProvider` in favor of their attribute counterparts.\n\nWe'll adapt core main & v12 to keep v12 backports\nsimple. The patch takes care of Tests/Unit and\nTests/UnitDeprecated, functional test need some\nadditional quirk for the test splitter to\ncontinue to work.\n\n> composer req --dev rector/rector\n> wget https://forge.typo3.org/attachments/download/38273/rector.php\n> find typo3/ -name \\*Test.php | grep Tests/Unit | xargs bin/rector process\n> rm rector.php\n> composer rem --dev rector/rector\n\nMinor manual adaption in ErrorHandlerTest.php and\nGeneralUtilityTest.php, and `runTests.sh -s cglGit`.\n\nNumber of executed unit tests and unitDeprecated tests\nshould stay the same.\n\nChange-Id: I63d2be40b8aa022f0918edd8dc1c360017316c46\nResolves: #103180\nReleases: main, 12.4\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83078\nTested-by: core-ci \nTested-by: Andreas Kienast \nTested-by: Christian Kuhn \nReviewed-by: Christian Kuhn \nReviewed-by: Stefan Bürk \nReviewed-by: Andreas Kienast \nTested-by: Stefan Bürk ","shortMessageHtmlLink":"[TASK] Use phpunit attributes over annotations"}},{"before":"291e32b7430c3ec2f6d735ec41b961ec41d22910","after":"664c50e88ae1da6455444b56bd8e42c550749780","ref":"refs/heads/main","pushedAt":"2024-02-21T09:06:24.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"TYPO3IncTeam","name":"TYPO3 GmbH","path":"/TYPO3IncTeam","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20440329?s=80&v=4"},"commit":{"message":"[TASK] Migrate input-group-addon to input-group-text\n\nResolves: #103167\nReleases: main\nChange-Id: Ic890b2b5ea50bd4410709912316e3da7ac0cad38\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83054\nTested-by: Andreas Kienast \nTested-by: Benjamin Franzke \nReviewed-by: Andreas Kienast \nReviewed-by: Benjamin Franzke \nTested-by: core-ci ","shortMessageHtmlLink":"[TASK] Migrate input-group-addon to input-group-text"}},{"before":"239d2616fb94ffee4e666ee90e28a9b402bfaf7b","after":"291e32b7430c3ec2f6d735ec41b961ec41d22910","ref":"refs/heads/main","pushedAt":"2024-02-14T17:56:27.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"TYPO3IncTeam","name":"TYPO3 GmbH","path":"/TYPO3IncTeam","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20440329?s=80&v=4"},"commit":{"message":"[BUGFIX] Fix tree example in styleguide\n\nSince the node is `collapsed` on initial\nrendering, the `aria-expanded` attribute\nis set to \"false\".\n\nResolves: #103119\nReleases: main\nChange-Id: Ia06d0a268cf572453b17f5bd332e7d482019b561\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82997\nTested-by: Jochen Roth \nTested-by: Oliver Bartsch \nReviewed-by: Jochen Roth \nTested-by: core-ci \nReviewed-by: Andreas Kienast \nTested-by: Andreas Kienast \nReviewed-by: Oliver Bartsch ","shortMessageHtmlLink":"[BUGFIX] Fix tree example in styleguide"}},{"before":"adc107e56c075e877be8e2fb15d61ac6c5a39dbb","after":"239d2616fb94ffee4e666ee90e28a9b402bfaf7b","ref":"refs/heads/main","pushedAt":"2024-02-14T07:30:28.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"TYPO3IncTeam","name":"TYPO3 GmbH","path":"/TYPO3IncTeam","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20440329?s=80&v=4"},"commit":{"message":"[BUGFIX] Respect TCA type `group` as `foreign_selector`\n\nIt's now possible to use a TCA type `group`\nfield as `foreign_selector` together with\nthe `useCombination` functionality. The\ncorresponding \"child child table\" information\nis in this case fetched from the `allowed`\noption.\n\nSide note: Using TCA type `group` for a\n`foreign_selector` field is not really\ndocumented, but it's also not forbidden.\nActually, it's a valid use case and also\nworking quite well as the new styleguide\nexamples demonstrate.\n\nHowever, the documentation should be adjusted\nto mention that only one table can be defined\nin `allowed` for such fields.\n\nResolves: #102904\nReleases: main, 12.4\nChange-Id: Icdde6a8acb1fb9166da8e6259758f6bf64d6c41f\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82721\nTested-by: Oliver Bartsch \nTested-by: core-ci \nReviewed-by: Benni Mack \nReviewed-by: Anja Leichsenring \nReviewed-by: Oliver Bartsch \nTested-by: Benni Mack \nTested-by: Anja Leichsenring ","shortMessageHtmlLink":"[BUGFIX] Respect TCA type group as foreign_selector"}},{"before":"41d764cc8fc2c389e0f716ce053225a53ce82cb8","after":"adc107e56c075e877be8e2fb15d61ac6c5a39dbb","ref":"refs/heads/main","pushedAt":"2024-02-13T13:00:29.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"TYPO3IncTeam","name":"TYPO3 GmbH","path":"/TYPO3IncTeam","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20440329?s=80&v=4"},"commit":{"message":"[TASK] Reduce TCA ctrl origUid usages\n\nThe database column defined by TCA ctrl 'origUid'\n('t3_origuid') had a bumpy ride over the years.\n\nIt was mostly obsoleted in v8 with the introduction of\n'translationSource' ('l10n_source'). A patch to fully\nremove it with #88495 has been reverted with #88501,\nleaving the field in limbo.\n\nThe only remaining \"true\" usage of 'origUid' is in an\ninline relation scenario in DataMapProcessor when an\ninline parent *is* localizable (TCA ctrl 'languageField'\nand 'transOrigPointerField' set), but a child *is not*:\nDue to the copy strategy of all inline children upon\nlocalization of a parent record, the core needs to know\nif a child exists already or needs to be created. 'origUid'\nthen stores the uid of the default language child. A couple\nof tests refer to this scenario as \"monoglot\" children.\n\nWe could potentially get rid of that scenario by\npostulating that an inline child has to be localizable\nas well if the parent is, but that decision can be\ntaken later.\n\nThe patch does not touch this scenario, but looks at\n'origUid' from a different perspective: If a table *is*\nlocalizable, or is not used as inline child, then 'origUid'\nis not needed. The patch thus removes TCA ctrl 'origUid'\nfrom TCA tables, keeping it only in the test scenario\nextensions 'test_irre_csv', 'test_irre_foreignfield' and\n'test_irre_foreignfield_non_ws'.\n\nThe bulk of the patch is about removing 't3_origuid' from\nthe functional test .csv fixture files, while the most\nimportant TCA changes are dropping ctrl 'origUid' from\ntable 'pages' and 'tt_content'.\n\nResolves: #103099\nRelated: #79856\nRelated: #88494\nRelated: #88495\nRelated: #88501\nReleases: main\nChange-Id: I622afde74294c389639974d312f121d0a6466b60\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82888\nTested-by: Oliver Klee \nReviewed-by: Benni Mack \nTested-by: Benni Mack \nTested-by: Stefan Bürk \nTested-by: Christian Kuhn \nReviewed-by: Stefan Bürk \nTested-by: core-ci \nReviewed-by: Christian Kuhn ","shortMessageHtmlLink":"[TASK] Reduce TCA ctrl origUid usages"}},{"before":"7d5c0f7f33a1f91b9cccbbbf868150d577b8111a","after":"6c736bf50ec698a1c0577c303bcab782101dc745","ref":"refs/heads/13.0","pushedAt":"2024-02-13T10:34:07.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"TYPO3IncTeam","name":"TYPO3 GmbH","path":"/TYPO3IncTeam","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20440329?s=80&v=4"},"commit":{"message":"[TASK] Set TYPO3 version to 13.0.2-dev\n\nChange-Id: I098521a44a34a15787fb547f760e508be96dc63a\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82968\nTested-by: Oliver Hader \nTested-by: core-ci \nReviewed-by: Oliver Hader ","shortMessageHtmlLink":"[TASK] Set TYPO3 version to 13.0.2-dev"}},{"before":"918131f87a90efcf7071c327e66588ffc547d5ad","after":"7d5c0f7f33a1f91b9cccbbbf868150d577b8111a","ref":"refs/heads/13.0","pushedAt":"2024-02-13T10:12:55.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"TYPO3IncTeam","name":"TYPO3 GmbH","path":"/TYPO3IncTeam","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20440329?s=80&v=4"},"commit":{"message":"[RELEASE] Release of TYPO3 13.0.1\n\nChange-Id: I020a5c47684aa4e9cc375a0ab2753f891d79f55b\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82967\nTested-by: Oliver Hader \nReviewed-by: Oliver Hader ","shortMessageHtmlLink":"[RELEASE] Release of TYPO3 13.0.1"}},{"before":"39cea42254133b63323a3d790fdbeb01a396f279","after":"41d764cc8fc2c389e0f716ce053225a53ce82cb8","ref":"refs/heads/main","pushedAt":"2024-02-13T08:49:33.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"TYPO3IncTeam","name":"TYPO3 GmbH","path":"/TYPO3IncTeam","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/20440329?s=80&v=4"},"commit":{"message":"[TASK] Do not force lightmode for examples\n\nThe style guide should aid in testing and constructing backend components.\nIn this change, we're removing the mandatory light mode for examples to\nenhance visibility of adjustments within sub-components.\n\nResolves: #103093\nReleases: main\nChange-Id: Ia838d75fdaccb48e4f43a0cdd9fa31e309603d2b\nReviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82879\nTested-by: Benjamin Franzke \nReviewed-by: Oliver Bartsch \nTested-by: core-ci \nReviewed-by: Benjamin Franzke \nTested-by: Oliver Bartsch ","shortMessageHtmlLink":"[TASK] Do not force lightmode for examples"}}],"hasNextPage":true,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"djE6ks8AAAAEYj4KlQA","startCursor":null,"endCursor":null}},"title":"Activity · TYPO3-CMS/styleguide"}