84652[FEATURE] Add CLI command `install:password:set`
Commit message
Review
-
Code review CR +2 Done
- Garvin Hicking +2
- Benjamin Franzke +1
-
Verified V +2 Done
- Garvin Hicking +2
- Benjamin Franzke +1
- core-ci +1 CI
Issues 2
Files 5
- typo3/sysext/core/Documentation/Changelog/14.0/Feature-104058-IntroduceInstallpasswordsetCommand.rstnew+56 −0
- typo3/sysext/core/Tests/Functional/Command/CliCommandTest.php+1 −0
- typo3/sysext/install/Classes/Command/PasswordSetCommand.php31new+97 −0
- typo3/sysext/install/Classes/ServiceProvider.php+23 −0
- typo3/sysext/install/Tests/Functional/Command/PasswordSetCommandTest.php7new+202 −0
Review log 85113
Show 6588 earlier messages
-
Rozbeh Chiryai Sharahi uploaded patch set 1 06/11/24, 21:37
-
core-ci voted on patch set 1 V -1 06/11/24, 21:41 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/59255
-
Rozbeh Chiryai Sharahi uploaded patch set 2
V -106/11/24, 21:49 -
core-ci voted on patch set 2 V +1 06/11/24, 21:53 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/59256
-
Stefan Bürk commented on patch set 2 06/12/24, 06:59
Would be nice to have a option which returns only the generated password, plain or as json so it can be used easily in scripts (for deployment processes / pipelines etc) - a.k.a. easy machine parsable. -
Rozbeh Chiryai Sharahi uploaded patch set 3
V +106/12/24, 08:52 -
Rozbeh Chiryai Sharahi commented on patch set 3 06/12/24, 08:54
Reply
Good idea. Will do that -
core-ci voted on patch set 3 V -1 06/12/24, 08:56 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/59289
-
Rozbeh Chiryai Sharahi uploaded patch set 4
V -106/12/24, 12:11 -
core-ci voted on patch set 4 V -1 06/12/24, 12:15 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/59319
-
Rozbeh Chiryai Sharahi uploaded patch set 5
V -106/12/24, 12:23 -
core-ci voted on patch set 5 V -1 06/12/24, 12:28 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/59320
-
Rozbeh Chiryai Sharahi uploaded patch set 6
V -106/12/24, 12:32 -
core-ci voted on patch set 6 V +1 06/12/24, 12:38 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/59323
-
Rozbeh Chiryai Sharahi commented on patch set 6 06/12/24, 12:45
Reply
As we have discussed in person: The commands scope is to update the install-tool-password and not to generate any kind of hashed-password. I renamed it to `install:password:set` and introduced the possibility for a dry option in case someone wants to manually add the password to his settings.php for some reason. Could you resolve this thread? -
Garvin Hicking commented on patch set 6 06/12/24, 13:17
What a great thing! Love the idea and your work on it, thanks! Would you like to add an accompanying feature RST file documenting the usage? Let me know if I can help with that. -
Rozbeh Chiryai Sharahi updated the commit message in patch set 7
V +106/12/24, 13:31 -
core-ci voted on patch set 7 V +1 06/12/24, 13:45 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/59330
-
Garvin Hicking commented on patch set 7 06/12/24, 13:57
Some more comments, hope they help.PasswordSetCommand.php:62This code comment refers to another file I think, would need a unique descriptionPasswordSetCommand.php:79This could maybe earn an extra check for actual stringlength or stringiness? Currently I can pass "--password=0" and would be asked for a password.PasswordSetCommand.php:102This seems to be unique in the core, but refers to a pretty old timestamp - did you copy this from somewhere maybe where the exception could would then create a dupe? To be sure, please use a current timestamp 😊RuntimeException.php:20Maybe use a unique name for this? Most other core extended RuntimeExceptions have a unique name to better indicate what they refer to, so in thise case somehting like a "ConsoleHelperNotFoundException" or something like that? -
Rozbeh Chiryai Sharahi commented on patch set 7 06/12/24, 14:21
PasswordSetCommand.php:62ReplyWow thanks for the review. Regarding the other points: Will address that all, give me a sec. Regarding exception number: I did not even know that we are always using the timestamp 😄 I simply added a random number and hoped it is not used. -
Rozbeh Chiryai Sharahi uploaded patch set 8
V +106/12/24, 14:39 -
Rozbeh Chiryai Sharahi commented on patch set 8 06/12/24, 14:40
Reply
I addressed all your comments. Could you set them to resolved in case they were addressed correctly to your opinion? -
core-ci voted on patch set 8 V +1 06/12/24, 14:43 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/59339
-
Rozbeh Chiryai Sharahi commented on patch set 8 06/12/24, 14:49
Reply
Yes, i will add a documentation, for sure. -
Garvin Hicking commented on patch set 8 06/12/24, 14:52
Thanks for addressing this so quick and your feedback. One issue is left for me about "--password" or "--password=0". Maybe if you review this with Stefan later he has valuable feedback on this. :-) Great work!PasswordSetCommand.php:62ReplyDonePasswordSetCommand.php:79ReplyI think this still has an issue. If I call with "--password=" it says "Password hashed: " (empty). I think in this case the auto-creation does need to kick in. Personally I would do a `if ((string)$password === '')`...?PasswordSetCommand.php:102ReplyDoneRuntimeException.php:20ReplyDone -
Rozbeh Chiryai Sharahi uploaded patch set 9
V +106/12/24, 15:28 -
core-ci voted on patch set 9 V -1 06/12/24, 15:36 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/59340
-
Garvin Hicking commented on patch set 9 06/12/24, 15:40
Feature-103956-IntroduceInstallpasswordsetCommand.rst:6I think you either need to use "Resolves: 103956" here, or the RST would need to reference feature 104058 instead. Also check out your commit message it says "Releases: 13" but "13" currently is main. So "Releases: main" would be sufficient.Feature-103956-IntroduceInstallpasswordsetCommand.rst:38What would this do, forcibly create a random password? In this case maybe write: "No interaction mode (auto-generated password)" ?Feature-103956-IntroduceInstallpasswordsetCommand.rst:47We usually write something like "The Install Tool password can now also be set via CLI instead of only via direct file access, allowing for more automation and easy hash generation without extra steps"...?PasswordSetCommand.php:99I think trim() makes a problem here. If I enter " " as a password it would actually be accepted as such and hashed...? Sorry if I am making this cumbersome, but I'd rather be very specific here than to create edge-cases :-) -
Rozbeh Chiryai Sharahi uploaded patch set 10
V -106/12/24, 15:46 -
Rozbeh Chiryai Sharahi uploaded patch set 11 06/12/24, 15:46
-
core-ci voted on patch set 10 V +1 06/12/24, 15:52 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/59342
-
Rozbeh Chiryai Sharahi commented on patch set 11 06/12/24, 15:52
Feature-103956-IntroduceInstallpasswordsetCommand.rst:38ReplyIf you provide --password=my-password it will hash it and place it If you do not provide a password it will generate one for youPasswordSetCommand.php:99ReplyThis was a mistake, i already fixed that in my later patch. I decided that doing `--password=` does not need some behaviour. No matter what is done in this case, it seems weird. So I throw now an exception: "Must not provide empty password as argument". -
Rozbeh Chiryai Sharahi commented on patch set 11 06/12/24, 15:55
Feature-103956-IntroduceInstallpasswordsetCommand.rst:6ReplyThanks for checking that. I am still a bit overwhelmed by documentation. Will try now to fix that.Feature-103956-IntroduceInstallpasswordsetCommand.rst:47Replythank you <3. I updated the message -
Rozbeh Chiryai Sharahi updated the commit message in patch set 12 06/12/24, 15:55
-
core-ci voted on patch set 11 V +1 06/12/24, 15:55 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/59343
-
Rozbeh Chiryai Sharahi uploaded patch set 13 06/12/24, 16:01
-
Rozbeh Chiryai Sharahi commented on patch set 12 06/12/24, 16:01
Feature-103956-IntroduceInstallpasswordsetCommand.rst:6ReplyAaaaah now I see what you mean. I just fixed the number. -
core-ci voted on patch set 12 V +1 06/12/24, 16:02 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/59346
-
core-ci voted on patch set 13 V +1 06/12/24, 16:11 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/59349
-
Garvin Hicking commented on patch set 13 06/12/24, 16:25
Thanks for iterating on this, resolved some comments. Couldn't test the latest iteration with empty/unset/0/null passwords, but I have hopes this works now. I'm sure Stefan will decide on the final implementation with a keen eye. :-)Feature-103956-IntroduceInstallpasswordsetCommand.rst:6ReplyDoneFeature-103956-IntroduceInstallpasswordsetCommand.rst:38ReplyDoneFeature-103956-IntroduceInstallpasswordsetCommand.rst:47ReplyI think this one is still missing, it shows "no impact" for me in the latest version?PasswordSetCommand.php:79ReplyDonePasswordSetCommand.php:99ReplyThat's a good solution, yes! -
Simon Schaufelberger updated the commit message in patch set 14
V +106/12/24, 17:38 -
Simon Schaufelberger commented on patch set 14 CR -1 06/12/24, 17:41
PasswordSetCommand.php:78please do not use is_null but use null comparison -
core-ci voted on patch set 14 V +1 06/12/24, 17:43 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/59360
-
Rozbeh Chiryai Sharahi uploaded patch set 15
CR -1V +106/12/24, 17:51 -
Rozbeh Chiryai Sharahi commented on patch set 14 06/12/24, 17:51
PasswordSetCommand.php:78ReplyDone -
core-ci voted on patch set 15 V +1 06/12/24, 17:58 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/59361
-
Garvin Hicking commented on patch set 15 06/12/24, 18:04
Feature-103956-IntroduceInstallpasswordsetCommand.rst:47ReplyDone -
Simon Schaufelberger commented on patch set 15 06/12/24, 21:12
PasswordSetCommand.php:107I would rather print something like: "QuestionHelper could not be loaded" -
Garvin Hicking commented on patch set 15 06/12/24, 21:18
PasswordSetCommand.php:107ReplySpeaking of - in which cases would these even happen? Are there symfony versions which are compatible but do not provide it? or is it shell/terminal dependant if the heloer is available? -
Rozbeh Chiryai Sharahi uploaded patch set 16
V +106/12/24, 21:35 -
Rozbeh Chiryai Sharahi commented on patch set 15 06/12/24, 21:37
PasswordSetCommand.php:107ReplygetHelper('question') return type returns a HelperInterface. So _theoretically_ IDE and php do not know that it will be a QuestionHelper. In future symfony versions, if ever, there might be a different instance comming out it will break as the methods return type expects a QuestionHelper. For me this is just a more controlled way to throw an exception saying "QuestionHelper could not be loaded", than expected return-type QuestionHelper but got something else. This was just the background of "why I did it that way". For now I addressed as @simonschaufi+typo3@gmail.com mentioned the exception-message. If you feel like it is better to dismiss the if-statement entirely, please let me know. -
core-ci voted on patch set 16 V +1 06/12/24, 21:40 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/59372
-
Georg Ringer commented on patch set 16 06/13/24, 05:55
Feature-104058-IntroduceInstallpasswordsetCommand.rst:48it is called Install Tool, please adopt it on other places as wellPasswordSetInvalidInputException.php:3declare strict missingPasswordSetCommand.php:86instead of "" and variable substitution we prefer sprintf IMHO, also belowPasswordSetCommand.php:94should we add a info message that the password is set as well?PasswordSetCommandTest.php:3declare strict -
Rozbeh Chiryai Sharahi commented on patch set 16 06/13/24, 07:51
Feature-104058-IntroduceInstallpasswordsetCommand.rst:48ReplyHey, wow, thanks for the Review! Will address that all. -
Rozbeh Chiryai Sharahi uploaded patch set 17
V +106/13/24, 08:13 -
Rozbeh Chiryai Sharahi commented on patch set 16 06/13/24, 08:14
Feature-104058-IntroduceInstallpasswordsetCommand.rst:48ReplyDonePasswordSetInvalidInputException.php:3ReplyDonePasswordSetCommand.php:86ReplyDonePasswordSetCommand.php:94ReplyAh yeah. I did that.PasswordSetCommandTest.php:3ReplyDone -
core-ci voted on patch set 17 V -1 06/13/24, 08:20 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/59422
-
Rozbeh Chiryai Sharahi uploaded patch set 18
V -106/13/24, 08:33 -
core-ci voted on patch set 18 V -1 06/13/24, 08:40 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/59427
-
Rozbeh Chiryai Sharahi uploaded patch set 19
V -106/13/24, 08:42 -
Rozbeh Chiryai Sharahi updated the commit message in patch set 20 06/13/24, 08:44
-
core-ci voted on patch set 19 V +1 06/13/24, 08:49 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/59429
-
core-ci voted on patch set 20 V +1 06/13/24, 08:54 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/59431
-
Stefan Bürk commented on patch set 20 CR -1 06/13/24, 14:25
ConsoleHelperNotFoundException.php:3Superflous - see comment in other file, this exception is not needed.PasswordSetInvalidInputException.php:2Missing a `declare(strict_types=1);`PasswordSetCommand.php:49I'm not a fan of having the write option as default. It would be better to have a option to explicity tell the command to write it (and at best to have the option to choose between `settings.php` or appending(creating) it to the `additional.php`. Having the not "destructive" option as default is better.PasswordSetCommand.php:107ReplyAdding this check and intruducing a dedicated exception class here does not make much sense. It does not help a user anyway and needs to be adressed in the core. Usually we simply use ``` /** @var QuestionHelper $questionHelper */ $questionHelper = $this->getHelper('question'); ``` if a method would not exists due to having a invalid class it would fail anyway. By putting it into a dedicated getter method you already added the check, so that manual check is here useless. A "Class xx is not compatible to xy" like type exception/fatal makes it more clear than the "unexpected helper retrieved" here. IMO such a change would pop up on symfony raises anyway, I'd say and thus fixed in the core before a release. Just ensure to add a test covering the helper retrival. I would remove the dedicated excpetion and check here and let the normal type check (return type) do the job.PasswordSetCommandTest.php:30Please add the new command also to the generic cli command testing in `\TYPO3\CMS\Core\Tests\Functional\Command\CliCommandTest`PasswordSetCommandTest.php:69File should be a) saved b) checked for changes c) restored to not pullate the functional testcase instance (as a safeguard) -
Stefan Bürk commented on patch set 20 06/13/24, 15:02
PasswordSetCommandTest.php:37+1 for not using TestCase properites for command/application creation and forgetting to tear them down. Nice. -
Rozbeh Chiryai Sharahi commented on patch set 20 06/13/24, 16:15
ConsoleHelperNotFoundException.php:3ReplySuper nice, thx for the review. Will address all this now. -
Rozbeh Chiryai Sharahi commented on patch set 20 06/13/24, 16:22
PasswordSetInvalidInputException.php:2ReplyThis was already solved in a more recent changeset, don't know why your comment is address change-set 15. -
Rozbeh Chiryai Sharahi uploaded patch set 21
CR -1V +106/13/24, 16:57 -
Rozbeh Chiryai Sharahi commented on patch set 21 06/13/24, 16:59
ConsoleHelperNotFoundException.php:3ReplyDonePasswordSetCommand.php:49ReplyAs we discussed in person, this would be addressed in an additional change to keep the scope down.PasswordSetCommand.php:107ReplyDonePasswordSetCommandTest.php:30ReplyDonePasswordSetCommandTest.php:69ReplyDone -
Rozbeh Chiryai Sharahi commented on patch set 21 06/13/24, 16:59
Reply
Done -
core-ci voted on patch set 21 V +1 06/13/24, 17:02 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/59516
-
Stefan Bürk voted on patch set 21 CR +1 V +1 06/13/24, 18:38
-
Georg Ringer commented on patch set 22
CR +1V +106/13/24, 18:53Published edit on patch set 21. -
Georg Ringer voted on patch set 22 CR +1 V +1 06/13/24, 18:53
-
core-ci voted on patch set 22 V +1 06/13/24, 18:57 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/59534
-
Garvin Hicking commented on patch set 22 CR -1 06/13/24, 18:57
Feature rst does not match current arguments / logic (writr vs dry) -
Rozbeh Chiryai Sharahi uploaded patch set 23
CR +1V +106/13/24, 19:22 -
Rozbeh Chiryai Sharahi commented on patch set 23 06/13/24, 19:22
Reply
jeeeeess, good eyes. 😄 -
core-ci voted on patch set 23 V +1 06/13/24, 19:27 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/59539
-
Stefan Bürk voted on patch set 23 CR +1 V +1 06/13/24, 19:33
-
Benjamin Franzke commented on patch set 23 CR -1 06/13/24, 19:53
Feature-104058-IntroduceInstallpasswordsetCommand.rst:37Let's avoid a password flag, passwords need to be read via interactive input. Reasons: Password can be read from shell history and the process list. -
Stefan Bürk voted on patch set 23 CR 0 V 0 06/13/24, 20:01
-
Rozbeh Chiryai Sharahi commented on patch set 23 06/13/24, 20:10
Feature-104058-IntroduceInstallpasswordsetCommand.rst:37ReplyHey, thx for the last minute catch 😄 ok i can do that. I don't remember why I added the `--password` option. Probably because I thought someone might want to set the password via CI in some weird scenarios. If setting a password programmatically is ever needed, than It will be a different patch 😊 -
Garvin Hicking commented on patch set 23 06/13/24, 20:37
Feature-104058-IntroduceInstallpasswordsetCommand.rst:37ReplyActually I would like if deployments and scripting could set install passwords programmatically via the CLI; docker instances could profit from it? at least passing it via ENV var if not command line argument...? -
Rozbeh Chiryai Sharahi commented on patch set 23 06/13/24, 20:53
Feature-104058-IntroduceInstallpasswordsetCommand.rst:37ReplyI was also considering env vars. Nevertheless is it ok for you to simply do this in a separate patch? I can follow up directly with such a patch, where we can fully focus on that one issue. -
Garvin Hicking commented on patch set 23 06/13/24, 20:59
Feature-104058-IntroduceInstallpasswordsetCommand.rst:37ReplySure, sorry - wasn't mean as a blocking issue, just a comment. I'm good to +1 either way, Stefan&Benjamin lead the way :) -
Rozbeh Chiryai Sharahi uploaded patch set 24
CR -1V +106/13/24, 21:03 -
Rozbeh Chiryai Sharahi commented on patch set 24 06/13/24, 21:04
Feature-104058-IntroduceInstallpasswordsetCommand.rst:37ReplyCool. So I removed the password option now (AND updated docs :D ).
-
core-ci voted on patch set 24 V +1 06/13/24, 21:07 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/59543
-
Garvin Hicking commented on patch set 24 CR +1 V +1 06/13/24, 21:11
Feature-104058-IntroduceInstallpasswordsetCommand.rst:37ReplyThinking about it; with a randomly generated password one can also do scripting; catch the output and operate on that. That could do for at least the deployment scenario I have in mind. Great you had the energy and motivation to keep this patch up. I promise you it's not always that hard 😅 -
Simon Schaufelberger wrote 06/13/24, 21:31
Removed reviewer Simon Schaufelberger. -
Rozbeh Chiryai Sharahi commented on patch set 24 06/14/24, 07:59
@stefan@buerk.tech @gh@faktor-e.de Does it make sense to first change the output format on default to json or yaml, so it is easier for machine learning? @stefan@buerk.tech brought me to this idea. I think for instance yaml is easy to read and also machine readable. Even json i think is fine, as it is an admin tool. (I can also introduce some output option: --output=json|yaml|human-readable -
Georg Ringer commented on patch set 24 06/14/24, 08:27
Reply
i am not sure if we should to add this for one single command?! -
Rozbeh Chiryai Sharahi commented on patch set 24 06/14/24, 10:14
Reply
Ok. Will resolve this again. -
Simon Schaufelberger uploaded patch set 25
CR +1V +108/06/24, 16:13 -
core-ci voted on patch set 25 V +1 08/06/24, 16:18 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/62958
-
Garvin Hicking commented on patch set 25 CR +1 V +1 08/07/24, 08:40
IMO this is quite well now! Tested again. -
Stefan Bürk commented on patch set 25 CR -1 08/07/24, 16:46
Feature-104058-IntroduceInstallpasswordsetCommand.rst:37ReplyBefore merging, @ben@bnf.dev should re-review this patch all his concerns has been solved properly. Thus -1 on this. -
Simon Schaufelberger commented on patch set 25 08/29/24, 12:10
Feature-104058-IntroduceInstallpasswordsetCommand.rst:37Replyping @ben@bnf.dev -
Juliane Wundermann uploaded patch set 26
CR +1V +105/05/25, 21:50 -
core-ci voted on patch set 26 V +1 05/05/25, 22:01 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/78558
-
Benjamin Franzke commented on patch set 26 06/26/25, 18:15
PasswordSetCommand.php:48I'd expect the command to *set* the password without any arguments supplied, having to specifiy `-w` explicitly is not intuitive. I'd rather see a `--dry-run` that would only print the hash, if specified, without saving it.PasswordSetCommand.php:71Hm, I feel like randomization should only be offered if explicitly requested via commandline flag (`-r/--random`). It's to easy to just click ENTER and have the password randomized without intent.PasswordSetCommand.php:78Let's not print the password hash if the password is written, it's not useful in this case and I'd rather not print hashes to the console if not actually needed. -
Garvin Hicking commented on patch set 26 CR -1 06/27/25, 07:49
on it -
Garvin Hicking commented on patch set 26 CR +1 V +1 06/27/25, 08:50
Adjusted the patch: - Write settings by default - Remove "--write" option in favor of reversed "--dry-run" logic - Only show password hash in "--no-interaction" mode - Reworked tests to match new workflows - Ensured tests have setUp/tearDown to preserve settings file and test for changes, using password validation. Added also checking the combined "no-interaction&dry-run" mode - Adapted docs, added note for CI/CD automation - Rebased, resolved conflicts -
Garvin Hicking commented on patch set 26 06/27/25, 08:54
Reply
DoneFeature-104058-IntroduceInstallpasswordsetCommand.rst:37ReplyDonePasswordSetCommand.php:48ReplyI see. This was the original setup but changed during the patch. However I do agree that when the command says "password:set" its default operation should not be to only do "password:dryset". ;)PasswordSetCommand.php:71Reply"--no-interaction" is basically the "--random" option, so we have that for intentional randmomizing. I do think that for the CLI feedback its a nice option to also use randomizing because people are used to having fallbacks kick in on empty inputs in a lot of Symfony commands. I would argue that this has a benefit so you can still decide on the "interaction" variant if you want to enter a password or let it get randomized. wdyt?PasswordSetCommand.php:78ReplyAck. I've changed this so only for dry-run the hash is emitted (for possible CI/CD automation, and also for the functional tests). -
Garvin Hicking uploaded patch set 27
CR +1V +106/27/25, 08:57 -
Garvin Hicking voted on patch set 27 CR +1 V +1 06/27/25, 08:57
-
core-ci voted on patch set 27 V +1 06/27/25, 09:06 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/81064
-
Benjamin Franzke uploaded patch set 28
CR +1V +107/04/25, 08:54 -
Benjamin Franzke commented on patch set 28 07/04/25, 08:54
PasswordSetCommand.php:71ReplyThanks for the refactorings, this looks very good now. Let's get it in 😊 -
core-ci voted on patch set 28 V +1 07/04/25, 09:02 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/81317
-
Garvin Hicking voted on patch set 28 CR +2 V +2 07/04/25, 09:18
-
Garvin Hicking merged patch set 29 07/04/25, 09:18