Specify the key module requirement in the composer.json with a caret symbol instead of hardcoding to a specific one

Created on 2 October 2024, 7 months ago

Updated 16 December 2024, 4 months ago

Problem/Motivation

Right now the module is hardcoded to the 1.19 version of drupal/key. This means if the module will have updates, then we cannot update to it until this module puts out a new version with updated dependencies. Using semantic versioning updating to a new minor should not break compatibility, so the best practice would be specifying version 1 of the key module like this:

        "drupal/key": "^1.19"

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

🐛 Bug report

Status

Needs review

Version

1.0

Component

Code

Created by

🇸🇰Slovakia kaszarobert

Live updates comments and jobs are added and updated live.

Merge Requests

!4Specify the key module requirement in the composer.json with a caret symbol instead of hardcoding to a specific one
Merged
🇨🇿Czech Republic milos.kroulik
updated 4 months ago

Comments & Activities

Issue created by @kaszarobert
Comment 4 months ago →
🇨🇿Czech Republic milos.kroulik
milos.kroulik → made their first commit to this issue’s fork.
Merge request !4Update composer.json → (Merged) created by milos.kroulik
Status changed to Fixed about 2 months ago2:07pm 10 March 2025
Comment about 2 months ago →
🇨🇿Czech Republic milos.kroulik
This is merged already, thanks @kaszarobert
Comment about 1 month ago →
System Message
Automatically closed - issue fixed for 2 weeks with no activity.

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024