Closed garvinhicking closed 1 year ago
@garvinhicking Thanks. I should simulate the whole process in the CI to avoid such regressions. Thanks. I have tried and fixed it with the latest release.
@sabbelasichon You rock, that's aweome. Seems to be working now for us! Many, many thanks. Have a nice family-weekend :-)
Same for you
Expected Behavior
Running deployment should use Symfony DI to build. I believe the recent update from @sabbelasichon (Thank you for your work!) made a change from Symfony DI 5.x to 6.x and a change in this commit:
https://github.com/TYPO3/Surf/compare/3.4.1...master#diff-32b7574ebf31b7df6df8cb142368104942b32cf39cd292acb02171f05479b92a
introced it. We get the error message below; sadly I'm a bit short on time and cannot investigate further, but if it doesn't ring a bell for any of you quickly, I can try to spend time on it in a few weeks. So long we revert back to the working 3.3.15 version.
Actual Behavior
An error appears about a non-existant service. See below.
Steps to Reproduce the Problem
Use this composer.json on a PHP 8.1 / 8.2 install:
Run composer install.
Here's our workflow definition (
Production.Staging.php
); there are a lot of config variables, you cannot use it directly, but maybe something is obviously wrong with it on how DI would need implentation now:Maybe it's relevant; our Production.Staging.php file actually looks like this:
and then the PHP-Code above is called
workflow.php
. We use this to have the same workflow for multiple recipes, depending on a base configuration.Now the actual error that we get:
Specifications