Changes in migrations for 5.4.0-alpha3

[muhme]

PR Type

Documentation

---

Description

• Update migration documentation for Joomla 5.4.0-alpha3

• Add new deprecations for UCM system and Random Image Module

• Expand automated core updates feature descriptions

• Include additional language string deprecations

---

Diagram Walkthrough

flowchart LR
  A["Migration Docs"] --> B["New Deprecations"]
  A --> C["New Features"]
  B --> D["UCM System"]
  B --> E["Random Image Module"]
  B --> F["Language Strings"]
  C --> G["Automated Updates"]
  C --> H["Filter Options"]

Loading

File Walkthrough

Relevant files

Documentation

new-deprecations.md Expand deprecations documentation with new entries              migrations/53-54/new-deprecations.md Add Random Image Module deprecations with method replacements Expand UCM system deprecation description with better formatting Include three new language string deprecations with replacements Improve formatting and structure throughout document +34/-15  new-features.md Enhance new features documentation with descriptions          migrations/53-54/new-features.md Add detailed description for Automated Core Updates feature Include additional PRs for automated updates functionality Add descriptions for 'None' filter options and user-friendly links Update version scope to include alpha3 features +17/-4

---

[qodo-merge-pro]

PR Reviewer Guide 🔍

(Review updated until commit 315b434)

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 2 🔵🔵⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Formatting Issue The Random Image Module section has inconsistent formatting with missing method class context and unclear deprecation guidance compared to other sections. ### Random Image Module [45648](https://github.com/joomla/joomla-cms/pull/45648) – Convert mod_random_image to service provider - ❌ Avoid using the `getRandomImage()` static method. - ✅ Instead use the non-static `getImage()` method. - ❌ Avoid using the `getImages()` static method. - ✅ Instead use the non-static `getImagesFromFolder()` method. - ❌ Avoid using the `getFolder()` static method. - ✅ Instead use the non-static `getSanitizedFolder()` method. Duplicate Entry The same PR link 45318 is listed twice with identical descriptions, which appears to be a copy-paste error. * [45318](https://github.com/joomla/joomla-cms/pull/45318) Added a link to more easily open the 'System – Maintenance – Database' view from the Pre-Update Check. * [45318](https://github.com/joomla/joomla-cms/pull/45318) Added a link to more easily open the 'Mail Templates' view from the Update Notification.

[muhme]

@richard67 please check and merge

[qodo-merge-pro]

PR Code Suggestions ✨

Latest suggestions up to 315b434
Explore these optional code suggestions:

Category	Suggestion	Impact
General	Add class name context The deprecation notice lacks the class name context, making it unclear which class contains these methods. Include the full class name to help developers identify the exact methods being deprecated. migrations/53-54/new-deprecations.md [35-40] -- ❌ Avoid using the `getRandomImage()` static method. +- ❌ Avoid using the `ModRandomImageHelper::getRandomImage()` static method. - ✅ Instead use the non-static `getImage()` method. -- ❌ Avoid using the `getImages()` static method. +- ❌ Avoid using the `ModRandomImageHelper::getImages()` static method. - ✅ Instead use the non-static `getImagesFromFolder()` method. -- ❌ Avoid using the `getFolder()` static method. +- ❌ Avoid using the `ModRandomImageHelper::getFolder()` static method. - ✅ Instead use the non-static `getSanitizedFolder()` method. Apply / Chat Suggestion importance[1-10]: 6 __ Why: The suggestion correctly identifies that the class name is missing for the deprecated methods, and adding it significantly improves the clarity of the documentation.	Low
Update

---

Previous suggestions

✅ Suggestions up to commit cff5d48

Category	Suggestion	Impact
General	Add missing class context The deprecation notice lacks the class name context, making it unclear which class contains these methods. Include the full class name to help developers identify exactly which methods are being deprecated. migrations/53-54/new-deprecations.md [35-40] -- ❌ Avoid using the `getRandomImage()` static method. +- ❌ Avoid using the `ModRandomImageHelper::getRandomImage()` static method. - ✅ Instead use the non-static `getImage()` method. -- ❌ Avoid using the `getImages()` static method. +- ❌ Avoid using the `ModRandomImageHelper::getImages()` static method. - ✅ Instead use the non-static `getImagesFromFolder()` method. -- ❌ Avoid using the `getFolder()` static method. +- ❌ Avoid using the `ModRandomImageHelper::getFolder()` static method. - ✅ Instead use the non-static `getSanitizedFolder()` method. Suggestion importance[1-10]: 6 __ Why: The suggestion correctly points out that the class name is missing for the deprecated methods, and adding it improves the clarity and precision of the documentation.	Low

[muhme]

Added at least one sentence for each feature as qodo sugested.

[richard67]

Thanks.