Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEATURE] Add support for TYPO3 13.0 #4

Merged
merged 8 commits into from
Mar 22, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 5, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
typo3/cms-backend (source) ^11.5 || ^12.4 -> ^11.5 || ^12.4 || ^13.0 age adoption passing confidence
typo3/cms-core (source) ^11.5 || ^12.4 -> ^11.5 || ^12.4 || ^13.0 age adoption passing confidence
typo3/cms-fluid (source) ^11.5 || ^12.4 -> ^11.5 || ^12.4 || ^13.0 age adoption passing confidence
typo3/cms-lowlevel (source) ^11.5 || ^12.4 -> ^11.5 || ^12.4 || ^13.0 age adoption passing confidence

Configuration

📅 Schedule: Branch creation - "every weekday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot added the dependencies Updates project dependencies label Mar 5, 2024
Copy link
Contributor Author

renovate bot commented Mar 5, 2024

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: composer.lock
Command failed: composer update typo3/cms-backend:13.0.1 typo3/cms-core:13.0.1 typo3/cms-fluid:13.0.1 typo3/cms-lowlevel:13.0.1 --with-dependencies --ignore-platform-req ext-intl --no-ansi --no-interaction --no-scripts --no-autoloader --no-plugins
Loading composer repositories with package information
Dependency psr/http-message is also a root requirement. Package has not been listed as an update argument, so keeping locked at old version. Use --with-all-dependencies (-W) to include root dependencies.
Dependency symfony/console is also a root requirement. Package has not been listed as an update argument, so keeping locked at old version. Use --with-all-dependencies (-W) to include root dependencies.
Dependency symfony/mailer is also a root requirement. Package has not been listed as an update argument, so keeping locked at old version. Use --with-all-dependencies (-W) to include root dependencies.
Dependency symfony/mime is also a root requirement. Package has not been listed as an update argument, so keeping locked at old version. Use --with-all-dependencies (-W) to include root dependencies.
Dependency typo3fluid/fluid is also a root requirement. Package has not been listed as an update argument, so keeping locked at old version. Use --with-all-dependencies (-W) to include root dependencies.
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires typo3/cms-core ^11.5 || ^12.4 || ^13.0, found typo3/cms-core[v11.5.0, ..., v11.5.36, v12.4.0, ..., v12.4.12, v13.0.0, v13.0.1] but these were not loaded, likely because it conflicts with another require.
  Problem 2
    - Root composer.json requires typo3/cms-fluid ^11.5 || ^12.4 || ^13.0, found typo3/cms-fluid[v11.5.0, ..., v11.5.36, v12.4.0, ..., v12.4.12, v13.0.0, v13.0.1] but these were not loaded, likely because it conflicts with another require.
  Problem 3
    - Root composer.json requires typo3/cms-backend ^11.5 || ^12.4 || ^13.0 -> satisfiable by typo3/cms-backend[v13.0.1].
    - typo3/cms-backend v13.0.1 requires typo3/cms-core 13.0.1 -> found typo3/cms-core[v13.0.1] but these were not loaded, likely because it conflicts with another require.
  Problem 4
    - saschaegerer/phpstan-typo3 is locked to version 1.10.0 and an update of this package was not requested.
    - saschaegerer/phpstan-typo3 1.10.0 requires typo3/cms-core ^10.4 || ^11.5 || ^12.4 || ^13.0 -> found typo3/cms-core[v10.4.0, ..., v10.4.37, v11.5.0, ..., v11.5.36, v12.4.0, ..., v12.4.12, v13.0.0, v13.0.1] but these were not loaded, likely because it conflicts with another require.
  Problem 5
    - Root composer.json requires typo3/cms-lowlevel ^11.5 || ^12.4 || ^13.0 -> satisfiable by typo3/cms-lowlevel[v13.0.1].
    - typo3/cms-lowlevel v13.0.1 requires typo3/cms-core 13.0.1 -> found typo3/cms-core[v13.0.1] but these were not loaded, likely because it conflicts with another require.
  Problem 6
    - typo3/testing-framework is locked to version 8.0.9 and an update of this package was not requested.
    - typo3/testing-framework 8.0.9 requires typo3/cms-core 12.*.*@dev || 13.*.*@dev -> found typo3/cms-core[v12.0.0, ..., v12.4.12, v13.0.0, v13.0.1] but these were not loaded, likely because it conflicts with another require.

Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

Copy link

codeclimate bot commented Mar 5, 2024

Code Climate has analyzed commit bb433c0 and detected 0 issues on this pull request.

The test coverage on the diff in this pull request is 100.0% (50% is the threshold).

This pull request will bring the total coverage in the repository to 0.0% (0.0% change).

View more on Code Climate.

@renovate renovate bot force-pushed the renovate/major-typo3-cms branch 20 times, most recently from 8645103 to 6362b5b Compare March 11, 2024 07:38
@renovate renovate bot force-pushed the renovate/major-typo3-cms branch 5 times, most recently from 67d0123 to 9f67b58 Compare March 18, 2024 08:15
@coveralls
Copy link
Collaborator

coveralls commented Mar 18, 2024

Pull Request Test Coverage Report for Build 8386881781

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 0.0%

Totals Coverage Status
Change from base Build 8323330005: 0.0%
Covered Lines: 0
Relevant Lines: 694

💛 - Coveralls

| datasource | package            | from    | to     |
| ---------- | ------------------ | ------- | ------ |
| packagist  | typo3/cms-backend  | 12.4.12 | 13.0.1 |
| packagist  | typo3/cms-core     | 12.4.12 | 13.0.1 |
| packagist  | typo3/cms-fluid    | 12.4.12 | 13.0.1 |
| packagist  | typo3/cms-lowlevel | 12.4.12 | 13.0.1 |
@renovate renovate bot force-pushed the renovate/major-typo3-cms branch from 9f67b58 to dcd3e2c Compare March 18, 2024 09:56
Copy link
Contributor Author

renovate bot commented Mar 22, 2024

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

Warning: custom changes will be lost.

@eliashaeussler eliashaeussler changed the title [TASK] Update TYPO3 CMS to v13 (major) [FEATURE] Add support for TYPO3 13.0 Mar 22, 2024
@eliashaeussler eliashaeussler added enhancement New feature or request and removed dependencies Updates project dependencies labels Mar 22, 2024
@eliashaeussler eliashaeussler merged commit 665845f into main Mar 22, 2024
23 checks passed
@eliashaeussler eliashaeussler deleted the renovate/major-typo3-cms branch March 22, 2024 07:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants