- Issue created by @mparker17
- 🇨🇦Canada mparker17 UTC-4
Created a patch. Moving to "Needs review" to prompt the community (and other maintainers) to review.
- Status changed to Needs review
8 months ago 11:50pm 13 August 2024 - 🇨🇦Canada mparker17 UTC-4
Determine if the Semantic Versioning spec says we should make a major version change, a minor version change, or a patch version change when we drop support for something outdated
I found https://github.com/semver/semver/issues/148 which suggests that I could even drop compatibility with older versions of Drupal core in a patch release (as long as I don't expose any part of Core's API or add any new features based on the newer versions).
Still researching this though.
- Status changed to Fixed
6 months ago 5:19pm 15 October 2024 - 🇨🇦Canada mparker17 UTC-4
I didn't hear any feedback in a few weeks, but experience with other modules suggests CI pipelines tend to work a bit better when you drop support in a new major version, so I created the
3.0.x
branch and I've dropped D9 support in that branch. Should hopefully see a release soon, depending on my free time. Automatically closed - issue fixed for 2 weeks with no activity.