typo3/class-alias-loader contains a Composer plugin which is blocked by your allow-plugins config. You may add it to the list if you consider it safe. You can run "composer config --no-plugins allow-plugins.typo3/class-alias-loader [true|false]" to enable it (true) or disable it explicitly and suppress this exception (false) See https://getcomposer.org/allow-plugins

typo3/class-alias-loader contains a Composer plugin which is blocked by your allow-plugins config. You may add it to the list if you consider it safe. You can run "composer config --no-plugins allow-plugins.typo3/class-alias-loader [true|false]" to enable it (true) or disable it explicitly and suppress this exception (false) See https://getcomposer.org/allow-plugins

Process completed with exit code 127.

The job was canceled because "false_7_4__10_4" failed.

Process completed with exit code 127.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires typo3/cms-core dev-master, found typo3/cms-core[dev-main, v8.7.7, ..., 8.7.x-dev, v9.0.0, ..., 9.5.x-dev, v10.0.0, ..., 10.4.x-dev, v11.0.0, ..., 11.5.x-dev, v12.0.0, ..., 12.4.x-dev, v13.0.0, ..., 13.2.x-dev (alias of dev-main)] but it does not match the constraint. Perhaps dev-master was renamed to dev-main? Problem 2 - Root composer.json requires typo3/cms-backend dev-master, found typo3/cms-backend[dev-main, v8.7.7, ..., 8.7.x-dev, v9.0.0, ..., 9.5.x-dev, v10.0.0, ..., 10.4.x-dev, v11.0.0, ..., 11.5.x-dev, v12.0.0, ..., 12.4.x-dev, v13.0.0, ..., 13.2.x-dev (alias of dev-main)] but it does not match the constraint. Perhaps dev-master was renamed to dev-main? Problem 3 - Root composer.json requires typo3/cms-extbase dev-master, found typo3/cms-extbase[dev-main, v8.7.7, ..., 8.7.x-dev, v9.0.0, ..., 9.5.x-dev, v10.0.0, ..., 10.4.x-dev, v11.0.0, ..., 11.5.x-dev, v12.0.0, ..., 12.4.x-dev, v13.0.0, ..., 13.2.x-dev (alias of dev-main)] but it does not match the constraint. Perhaps dev-master was renamed to dev-main? Problem 4 - Root composer.json requires typo3/cms-extensionmanager dev-master, found typo3/cms-extensionmanager[dev-main, v8.7.7, ..., 8.7.x-dev, v9.0.0, ..., 9.5.x-dev, v10.0.0, ..., 10.4.x-dev, v11.0.0, ..., 11.5.x-dev, v12.0.0, ..., 12.4.x-dev, v13.0.0, ..., 13.2.x-dev (alias of dev-main)] but it does not match the constraint. Perhaps dev-master was renamed to dev-main? Problem 5 - Root composer.json requires typo3/cms-fluid dev-master, found typo3/cms-fluid[dev-main, v8.7.7, ..., 8.7.x-dev, v9.0.0, ..., 9.5.x-dev, v10.0.0, ..., 10.4.x-dev, v11.0.0, ..., 11.5.x-dev, v12.0.0, ..., 12.4.x-dev, v13.0.0, ..., 13.2.x-dev (alias of dev-main)] but it does not match the constraint. Perhaps dev-master was renamed to dev-main? Problem 6 - Root composer.json requires typo3/cms-frontend dev-master, found typo3/cms-frontend[dev-main, v8.7.7, ..., 8.7.x-dev, v9.0.0, ..., 9.5.x-dev, v10.0.0, ..., 10.4.x-dev, v11.0.0, ..., 11.5.x-dev, v12.0.0, ..., 12.4.x-dev, v13.0.0, ..., 13.2.x-dev (alias of dev-main)] but it does not match the constraint. Perhaps dev-master was renamed to dev-main? Problem 7 - typo3/testing-framework[6.3.0, ..., 6.x-dev] require typo3/cms-core 10.*.*@dev || 11.*.*@dev -> found typo3/cms-core[v10.0.0, ..., 10.4.x-dev, v11.0.0, ..., 11.5.x-dev] but it conflicts with your root composer.json require (dev-master). - typo3/testing-framework[6.0.0-alpha, ..., 6.2.5] require typo3/cms-core 10.*.*@dev -> found typo3/cms-core[v10.0.0, ..., 10.4.x-dev] but it conflicts with your root composer.json require (dev-master). - Root composer.json requires typo3/testing-framework v6.x -> satisfiable by typo3/testing-framework[6.0.0-alpha, ..., 6.x-dev].

typo3/class-alias-loader contains a Composer plugin which is blocked by your allow-plugins config. You may add it to the list if you consider it safe. You can run "composer config --no-plugins allow-plugins.typo3/class-alias-loader [true|false]" to enable it (true) or disable it explicitly and suppress this exception (false) See https://getcomposer.org/allow-plugins

The job was canceled because "false_7_4__10_4" failed.

typo3/class-alias-loader contains a Composer plugin which is blocked by your allow-plugins config. You may add it to the list if you consider it safe. You can run "composer config --no-plugins allow-plugins.typo3/class-alias-loader [true|false]" to enable it (true) or disable it explicitly and suppress this exception (false) See https://getcomposer.org/allow-plugins

typo3/class-alias-loader contains a Composer plugin which is blocked by your allow-plugins config. You may add it to the list if you consider it safe. You can run "composer config --no-plugins allow-plugins.typo3/class-alias-loader [true|false]" to enable it (true) or disable it explicitly and suppress this exception (false) See https://getcomposer.org/allow-plugins

Process completed with exit code 127.

The job was canceled because "false_7_4__10_4" failed.

Your requirements could not be resolved to an installable set of packages. Problem 1 - typo3/testing-framework[6.0.0, ..., 6.2.5] require typo3/cms-core 10.*.*@dev -> found typo3/cms-core[v10.0.0, ..., v10.4.37] but it conflicts with your root composer.json require (^9.5). - typo3/testing-framework[6.3.0, ..., 6.16.9] require typo3/cms-core 10.*.*@dev || 11.*.*@dev -> found typo3/cms-core[v10.0.0, ..., v10.4.37, v11.0.0, ..., v11.5.37] but it conflicts with your root composer.json require (^9.5). - Root composer.json requires typo3/testing-framework v6.x -> satisfiable by typo3/testing-framework[6.0.0, ..., 6.16.9].

typo3/class-alias-loader contains a Composer plugin which is blocked by your allow-plugins config. You may add it to the list if you consider it safe. You can run "composer config --no-plugins allow-plugins.typo3/class-alias-loader [true|false]" to enable it (true) or disable it explicitly and suppress this exception (false) See https://getcomposer.org/allow-plugins

Process completed with exit code 127.

The job was canceled because "false_7_4__10_4" failed.

Your requirements could not be resolved to an installable set of packages. Problem 1 - typo3/testing-framework[6.3.0, ..., 6.x-dev] require typo3/cms-core 10.*.*@dev || 11.*.*@dev -> found typo3/cms-core[v10.0.0, ..., 10.4.x-dev, v11.0.0, ..., 11.5.x-dev] but it conflicts with your root composer.json require (9.5.x-dev). - typo3/testing-framework[6.0.0-alpha, ..., 6.2.5] require typo3/cms-core 10.*.*@dev -> found typo3/cms-core[v10.0.0, ..., 10.4.x-dev] but it conflicts with your root composer.json require (9.5.x-dev). - Root composer.json requires typo3/testing-framework v6.x -> satisfiable by typo3/testing-framework[6.0.0-alpha, ..., 6.x-dev].

typo3/class-alias-loader contains a Composer plugin which is blocked by your allow-plugins config. You may add it to the list if you consider it safe. You can run "composer config --no-plugins allow-plugins.typo3/class-alias-loader [true|false]" to enable it (true) or disable it explicitly and suppress this exception (false) See https://getcomposer.org/allow-plugins

Process completed with exit code 127.

The job was canceled because "false_7_4__10_4" failed.

The operation was canceled.

The job was canceled because "false_7_4__10_4" failed.

The operation was canceled.

The job was canceled because "false_7_4__10_4" failed.

Your requirements could not be resolved to an installable set of packages. Problem 1 - typo3/testing-framework[6.0.0, ..., 6.2.5] require typo3/cms-core 10.*.*@dev -> found typo3/cms-core[v10.0.0, ..., v10.4.37] but it conflicts with your root composer.json require (^9.5). - typo3/testing-framework[6.3.0, ..., 6.16.9] require typo3/cms-core 10.*.*@dev || 11.*.*@dev -> found typo3/cms-core[v10.0.0, ..., v10.4.37, v11.0.0, ..., v11.5.37] but it conflicts with your root composer.json require (^9.5). - Root composer.json requires typo3/testing-framework v6.x -> satisfiable by typo3/testing-framework[6.0.0, ..., 6.16.9].

typo3/class-alias-loader contains a Composer plugin which is blocked by your allow-plugins config. You may add it to the list if you consider it safe. You can run "composer config --no-plugins allow-plugins.typo3/class-alias-loader [true|false]" to enable it (true) or disable it explicitly and suppress this exception (false) See https://getcomposer.org/allow-plugins

The operation was canceled.

The job was canceled because "false_7_4__10_4" failed.

typo3/class-alias-loader contains a Composer plugin which is blocked by your allow-plugins config. You may add it to the list if you consider it safe. You can run "composer config --no-plugins allow-plugins.typo3/class-alias-loader [true|false]" to enable it (true) or disable it explicitly and suppress this exception (false) See https://getcomposer.org/allow-plugins

typo3/class-alias-loader contains a Composer plugin which is blocked by your allow-plugins config. You may add it to the list if you consider it safe. You can run "composer config --no-plugins allow-plugins.typo3/class-alias-loader [true|false]" to enable it (true) or disable it explicitly and suppress this exception (false) See https://getcomposer.org/allow-plugins

The operation was canceled.

The job was canceled because "false_7_4__10_4" failed.

typo3/class-alias-loader contains a Composer plugin which is blocked by your allow-plugins config. You may add it to the list if you consider it safe. You can run "composer config --no-plugins allow-plugins.typo3/class-alias-loader [true|false]" to enable it (true) or disable it explicitly and suppress this exception (false) See https://getcomposer.org/allow-plugins

typo3/class-alias-loader contains a Composer plugin which is blocked by your allow-plugins config. You may add it to the list if you consider it safe. You can run "composer config --no-plugins allow-plugins.typo3/class-alias-loader [true|false]" to enable it (true) or disable it explicitly and suppress this exception (false) See https://getcomposer.org/allow-plugins

The operation was canceled.

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v2, actions/cache@v2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/