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

Update dependency doctrine/persistence to v4 #108

Open
wants to merge 1 commit into
base: 2.1.x
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 2, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
doctrine/persistence (source) ^2.0 || ^3.0 -> ^2.0 || ^3.0 || ^4.0 age adoption passing confidence

Release Notes

doctrine/persistence (doctrine/persistence)

v4.0.0

Compare Source

Release Notes for 4.0.0

Backwards incompatible release (major)

4.0.0
  • Total issues resolved: 0
  • Total pull requests resolved: 6
  • Total contributors: 2
BC Break

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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 this update again.


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

Read more information about the use of Renovate Bot within LM-Commons.

Copy link
Contributor Author

renovate bot commented Nov 2, 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 doctrine/persistence:4.0.0 --with-dependencies --ignore-platform-req='ext-*' --ignore-platform-req='lib-*' --no-ansi --no-interaction --no-scripts --no-autoloader --no-plugins
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires doctrine/persistence ^2.0 || ^3.0 || ^4.0, found doctrine/persistence[2.0.0, ..., 2.5.7, 3.0.0, ..., 3.4.0, 4.0.0] but these were not loaded, likely because it conflicts with another require.
  Problem 2
    - doctrine/orm is locked to version 3.3.0 and an update of this package was not requested.
    - doctrine/orm 3.3.0 requires doctrine/persistence ^3.3.1 -> found doctrine/persistence[3.3.1, 3.3.2, 3.3.3, 3.4.0] but it conflicts with your temporary update constraint (doctrine/persistence:4.0.0).

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

@renovate renovate bot added the renovate label Nov 2, 2024
@renovate renovate bot force-pushed the renovate/doctrine-persistence-4.x branch from 682cdd3 to 229d0aa Compare November 4, 2024 03:34
@renovate renovate bot force-pushed the renovate/doctrine-persistence-4.x branch 2 times, most recently from 3f26000 to ce191c5 Compare November 18, 2024 03:36
| datasource | package              | from  | to    |
| ---------- | -------------------- | ----- | ----- |
| packagist  | doctrine/persistence | 3.4.0 | 4.0.0 |


Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
@renovate renovate bot force-pushed the renovate/doctrine-persistence-4.x branch from ce191c5 to 7751907 Compare December 1, 2024 10:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: 🆕 New
Development

Successfully merging this pull request may close these issues.

0 participants