Follow semantic versioning rules

Created on 5 September 2023, over 1 year ago

Problem/Motivation

My drupal installation has thunder/thunder-distribution 6.2.0 installed, which requires drupal/entity_browser 2.5.
Entity browser has a bug that has been fixed in version 2.6, and I wanted to upgrade entity_browser. Unfortunately thunder 6.2.0 requires the exact version 2.5, so I have to upgrade thunder as well.

Unfortunately thunder does not follow the semantic versioning rules, and version 6.2.1 introduces a "big new feature":

This release is a bit larger than usually. While it contains some smaller bugfixes and module updates, the release is also adding one of the biggest features we had in a while.

This big fat feature requires the installation of graphql 4, while the environment my drupal installation is living in depends on graphql 3.

So now I'm stuck with a broken entity_browser because I can't upgrade to the next patch level release of thunder, because thunder does not follow semver, and there is no space between 6.2.0 and 6.2.1 for a bugfix release.

Proposed resolution

Follow semantic versioning rules and do not ship new features in patch level releases.

Feature request
Status

Active

Version

6.2

Component

Miscellaneous

Created by

🇩🇪Germany cweiske

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Production build 0.71.5 2024