Overview of merged pull requests
BUGFIX: disable invisible composer interaction in `./flow package:create <https://github.com/neos/flow-development-collection/pull/2926>`_
with #2571 <https://github.com/neos/flow-development-collection/issues/2571>``_was introduced, that the composer subcommand used by `./flow package:create`` hides its output. But using the ``new NullOutput()` doesn’t prevent any interaction initiated by composer such as the infamous:
> neos/composer-plugin contains a Composer plugin which is currently not in your allow-plugins config. See https://getcomposer.org/allow-plugins > Do you trust “neos/composer-plugin” to execute code and wish to enable it now? (writes “allow-plugins” to composer.json) [y,n,d,?]
the current problem is that composer asks this question but shows not output. So one has to blind input
y without even knowing the question. This is perceived as bug but clearly a feature see #2757.
With this bugfix we use the official supported cli flag
--quiet to archive the same as the NullOutput and furthermore disable any invisible requested interactivity.
in the above case instead of a question - an error will be thrown, which is understandable and fixable by the user:
> In PluginManager.php line 768: > neos/composer-plugin contains a Composer plugin which is blocked by your allow-plugins config. You may add it to the list if you consider it safe. > … > The installation was not successful. > Composer returned the error code: 1 > > Type: Neos\Flow\Package\Exception > Code: 1572187932 > File: Packages/Framework/Neos.Flow/Classes/Package/PackageManager.php > Line: 391 > > Open Data/Logs/Exceptions/202210221257240bfbde.txt for a full stack trace.
This renders API docs (again), using Doctum via GH Actions.
The results are pushed to https://neos.github.io for consumption.
A test run result can be seen at https://neos.github.io/flow/8.2/index.html already. The workflow run is visible at https://github.com/kdambekalns/flow-development-collection/actions/runs/3233003582/jobs/5294292366
See also #1
[x] Links to GitHub are wrong (
workspacemust go and branch is wrong)
[ ] Maybe add a theme to make it look more Neos-y?
Precomposing a hash on cache warmup will make sure that the used hash to prevent timing attack always reflects the current configuration.
Previously there was a bcrypt password with the cost of 16 hard coded in but the configuration was set to 14 as default.
Fixes #3908 reported by @Benjamin-K
Update the cli command example in the documentation to follow best practices. In commands, when showing a progress bar, using ->progressFinish() does not output a newline. This is intended, as it allows adding further text in the same line. However, the full command output - unless empty - should end with a newline.