The 'core_version_requirement' constraint (9.5.10) requires the 'core' key not be set in modules/contrib/webform_select_collection/tests/modules/wsc_test/wsc_test.info.yml

Created on 20 June 2024, 5 months ago

Updated 24 June 2024, 5 months ago

Problem/Motivation

Running drush commands that check your project for various issues triggers the error in the title, causing those commands to fail. The code that throws this error is Drupal\Core\Extension\InfoParserDynamic.

Steps to reproduce

Use this module in your project and run a drush command such as cache-rebuild or updb.

Proposed resolution

Update the test module info file to use core_version_requirement instead of core and make that match the core_version_requirement of the project itself.

🐛 Bug report

Status

Active

Version

1.2

Component

Code

Created by

🇨🇦Canada teknocat

Live updates comments and jobs are added and updated live.

Merge Requests

!5The 'core_version_requirement' constraint (9.5.10) requires the 'core' key not be set in modules/contrib/webform_select_collection/tests/modules/wsc_test/wsc_test.info.yml
Open
🇨🇦Canada teknocat
updated 5 months ago

Comments & Activities

Issue created by @teknocat
Merge request !5Update test module info file for proper D9+ compatibility → (Open) created by teknocat
Comment 5 months ago →
🇨🇦Canada teknocat
teknocat → changed the visibility of the branch 3456062-the-coreversionrequirement-constraint to hidden.
Pipeline finished with Failed
5 months ago
Total: 209s
#204084
Comment 5 months ago →
🇨🇦Canada teknocat
The eslint error in the merge pipeline applies to Javascript that I didn't touch. I don't quite know why it's flagging ONLY the call to .val() in that one spot when it calls the jQuery .val() method several places prior to that. Anyway, it's not an issue in terms of merging and then releasing a new version with the compatibility fix in place.

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024