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 Drupal Core to v11.0.10 (patch) #14

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 7, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
drupal/core-composer-scaffold (source) 11.0.5 -> 11.0.10 age adoption passing confidence
drupal/core-dev-pinned 11.0.5 -> 11.0.10 age adoption passing confidence

Release Notes

drupal/core-composer-scaffold (drupal/core-composer-scaffold)

v11.0.10

Compare Source

v11.0.9

Compare Source

v11.0.8

Compare Source

v11.0.7

Compare Source

v11.0.6

Compare Source

drupal/core-dev-pinned (drupal/core-dev-pinned)

v11.0.10

Compare Source

v11.0.9

Compare Source

v11.0.8

Compare Source

v11.0.7

Compare Source

v11.0.6

Compare Source


Configuration

📅 Schedule: Branch creation - "after 10pm every weekday,every weekend,before 5am every weekday" in timezone Europe/Helsinki, Automerge - At any time (no schedule defined).

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

Rebasing: Whenever PR becomes conflicted, 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 was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/patch-drupal-core branch from d2da037 to eac04d8 Compare November 12, 2024 12:59
@renovate renovate bot changed the title Update Drupal Core to v11.0.6 (patch) Update Drupal Core to v11.0.7 (patch) Nov 12, 2024
@renovate renovate bot force-pushed the renovate/patch-drupal-core branch from eac04d8 to 58e6d8e Compare November 20, 2024 21:15
@renovate renovate bot changed the title Update Drupal Core to v11.0.7 (patch) Update Drupal Core to v11.0.8 (patch) Nov 20, 2024
@renovate renovate bot force-pushed the renovate/patch-drupal-core branch from 58e6d8e to 47f290f Compare November 22, 2024 17:05
@renovate renovate bot changed the title Update Drupal Core to v11.0.8 (patch) Update Drupal Core to v11.0.9 (patch) Nov 22, 2024
@renovate renovate bot removed the drupal label Dec 10, 2024
@renovate renovate bot force-pushed the renovate/patch-drupal-core branch from 47f290f to 8e387d3 Compare January 7, 2025 02:33
@renovate renovate bot changed the title Update Drupal Core to v11.0.9 (patch) Update Drupal Core to v11.0.10 (patch) Jan 7, 2025
Copy link
Contributor Author

renovate bot commented Jan 7, 2025

⚠️ 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 drupal/core-composer-scaffold:11.0.10 drupal/core-dev-pinned:11.0.10 --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 drupal/core-dev-pinned 11.0.10 -> satisfiable by drupal/core-dev-pinned[11.0.10].
    - drupal/core-dev-pinned 11.0.10 requires drupal/core 11.0.10 -> found drupal/core[11.0.10] 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants