DOC silverstripe/widgets removed

en/04_Changelogs/5.1.0.md

@@ -10,6 +10,7 @@ title: 5.1.0 (unreleased)
   - [Eager loading](#eager-loading)
   - [Other new features](#other-features)
 - [API changes](#api-changes)
+- [Dependency changes](#dependency-changes)
 - [Bug fixes](#bug-fixes)
 
 ## Features and enhancements
@@ -49,6 +50,10 @@ Read more about [eager loading](/developer_guides/model/relations/#eager-loading
 
 - [`BuildTask`](api:SilverStripe\Dev\BuildTask) now has boolean `is_enabled` configuration option which has precedence over the existing `BuildTask::enabled` protected class property. The `BuildTask::enabled` property has been marked as deprecated and will be removed in CMS 6 if favour of using `is_enabled` instead.
 
+## Dependency changes
+
+- The unsupported modules `silverstripe/widgets` and `silverstripe/content-widget` were removed from `silverstripe/recipe-blog`. They were accidentally included in the `2.0.0` release of `silverstripe/recipe-blog`. The `silverstripe/widgets` and `silverstripe/content-widget` modules are CMS-5-compatible though unsupported. If your project relies on `silverstripe/widgets` or `silverstripe/content-widget`, manually update your project's `composer.json` file to explicitly require these modules.
+
 ## Bug fixes
 
 - [`DataList::filterAny()`](api:SilverStripe\ORM\DataList::filterAny()) queries on many-many relations that use an aggregate `HAVING` clause now correctly use an `OR` conjunction rather than an incorrect `AND` conjunction.