The installed Composer packages will be different depending on the
major TYPO3 version being tested and on the strategy for the
dependencies (highest, lowest). So it makes sense to have
separate Composer caches for these versions in order to avoid
cache misses.
The CI workflow with predefined GitHub actions had an empty `on:`
element, which is invalid. Use the correct event for manually
triggered workflow runs instead.
It might happen, when starting the fuctional test that the database service container is not ready yet.
This patch provides an extra timeout to wait for the service to make sure the test does not fail because of missing database.
The `xargs` shell command will throw an error if find will return an empty result.
Adding `-r` will prevent this error.
Example:
A project has no yml files.
- Before: The yaml-linting fails.
- With that patch: The yaml-linting succeed.
Now that we have added support for TYPO3 11LTS, we have been supporting
3 different TYPO3 LTS versions in the same branch. This has turned out
to be too much of a hassle when running the test. So now is the time
to drop support for 9LTS.
It has turned out that having builds only for pushes (but not
pull requests) is not enough for triggering builds for PRs
from forks.
So we will need to live with pushes to non-PR branches other
than main not triggering a build, and having to create a
dummy draft PR for testing the CI build.
This reverts commit d1f02afe79.
Fixes#359
This will allow us to test things on the CI pipeline without
having to create a dummy/draft PR for this.
Hopefully, this will also allow builds for forks.
Composer versions 2.2.0 and 2.2.1 have a bug that breaks PHPUnit.
Until version 2.2.2 is released with a fix, we need to keep to
Composer 2.1 to keep the tests from breaking.
See https://github.com/composer/composer/issues/10387 for details.
The badge behaves in an unpredictable way if there are mutiple unstable
releases (which happens when we update the branch alias for the `main`
branch) and hence is pretty much useless.
The previous configuration disallowed newlines in ternary operator like:
$a = $condition1 && $condition2
? $foo_man_this_is_too_long_what_should_i_do
: $bar;
This seems very arbitrary since breaking on other operators is in fact
allowed.
This change allows such longer statements to be broken apart over
several lines.
This fixes a missing Symfony polyfill for `str_starts_with` in
TYPO3 11.5.0 and 11.5.1, which fixes a crash in the unit tests with
TYPO3 11LTS and PHP 7.4 using the lowest possible Composer dependencies.
If the CI build will do a composer update in the next step anyway,
there is no need to actually install any packages when requiring
the desired TYPO3 version.
Fixes#324
