[Tracker]
Update Summary: [One-line status update for stakeholders]
Short Description: [One-line issue summary for stakeholders]
Check-in Date: MM/DD/YYYY
Metadata is used by the AI Tracker. Docs and additional fields here.
[/Tracker]

Problem/Motivation

Your requirements could not be resolved to an installable set of packages.
  Problem 1
    - Root composer.json requires drupal/core-dev 11.1.9 -> satisfiable by drupal/core-dev[11.1.9].
    - composer/composer[2.9.3, ..., 2.9.x-dev] require justinrainbow/json-schema ^6.5.1 -> satisfiable by justinrainbow/json-schema[6.5.1, ..., 6.6.4].
    - drupal/core-dev 11.1.9 requires composer/composer ^2.8.1 -> satisfiable by composer/composer[2.9.3, 2.9.x-dev].
    - drupal/core-dev 11.1.9 requires justinrainbow/json-schema ^5.2 -> satisfiable by justinrainbow/json-schema[5.2.0, ..., 5.x-dev].
    - Conclusion: don't install justinrainbow/json-schema 5.3.1 (conflict analysis result)
    - You can only install one version of a package, so only one of these can be installed: justinrainbow/json-schema[5.2.0, ..., 5.x-dev, 6.5.2, ..., 6.6.4].

Steps to reproduce (required for bugs, but not feature requests)

Specifically on 11.1.9 there is a missmatch.

Proposed resolution

Figure out the dependency missmatch and fix it.

Issue fork ai-3565610

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

marcus_johansson created an issue. See original summary.

marcus_johansson’s picture

marcus_johansson commented
Assigned: marcus_johansson » Unassigned
Status: Active » Needs review

Turns out to be a core issue not compatible with Composer - it will not be fixed, since 11.3.0 is imminent and 11.2.x will be the previous minor. See: https://drupal.slack.com/archives/CGKLP028K/p1767266754103319

Meaning the solution for now is that we turn off previous minor, until 11.3.0 is released and a follow-up issue exists here: #3565612: Turn on previous minor testing when Drupal 11.3.0 is released.

marcus_johansson opened merge request !1076

marcus_johansson’s picture

marcus_johansson commented
Issue tags: +needs backport to 1.1.x, +Needs upstream bugfix

Code exists for turning of previous minor temporarily.

svendecabooter’s picture

svendecabooter
he/him
Primary language Dutch
Location Gent
commented

I was able to fix this for another contrib project by adding audit config to the composer.json file.
Not sure if that's the best approach: https://git.drupalcode.org/project/webform_encrypt/-/merge_requests/12/d...

I think this is also related to https://www.drupal.org/project/gitlab_templates/issues/3564269
Turning off previous minor until the issue above is fixed, might be the most safe approach...
That issue would need to be tracked, to reactivate the previous minor job then, once it gets fixed.

abhisekmazumdar’s picture

abhisekmazumdar
he/him
Primary language English
Location India
commented

The changes look good, and as per the discussion over Slack, this is a temporary workaround until the upstream GitLab template version tag is created with the latest fix. RTBC from my side.

marcus_johansson’s picture

marcus_johansson commented
Status: Needs review » Fixed

Artem found this file via the file that gets downloaded on our CI, which leads to #3404175: Adopt (semver) versioning for gitlab_templates.

Seems like the fix is that the main branch for the ref is now main until Gitlab template is released in 2.x branch, instead of the variable they used.

Will merge this and push down and upstream.

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.