Added mention about LTS updates in the update doc (#2694)

mnocon · dabrt · mnocon · commit c26dca281bb7 · 2025-04-15T09:36:02.000+02:00
* Added mention about LTS updates

* Support portal -&gt; Service portal

* Apply suggestions from code review

Co-authored-by: Tomasz Dąbrowski &lt;64841871+dabrt@users.noreply.github.com&gt;

* Update docs/resources/contributing/report_and_follow_issues.md

* Unified occurances to "Service portal"

---------

Co-authored-by: Tomasz Dąbrowski &lt;64841871+dabrt@users.noreply.github.com&gt;
diff --git a/docs/getting_started/install_ibexa_dxp.md b/docs/getting_started/install_ibexa_dxp.md
@@ -60,7 +60,7 @@ composer -V
 The site is password-protected.
 You must set up authentication tokens to access the site.
 
-Log in to your service portal on [support.ibexa.co](https://support.ibexa.co/), go to your **Service Portal**, and look for the following on the **Maintenance and Support agreement details** screen:
+Log in to your Service portal on [support.ibexa.co](https://support.ibexa.co/), go to your **Service Portal**, and look for the following on the **Maintenance and Support agreement details** screen:
 
 ![Authentication token](using_composer_auth_token.png)
 
@@ -93,7 +93,7 @@ This allows you to revoke access later.
 After this, when running Composer to get updates, you're asked for a username and password.
 Use:
 
-- as username - your Installation key found on the **Maintenance and Support agreement details** page in the service portal
+- as username - your Installation key found on the **Maintenance and Support agreement details** page in the Service portal
 - as password - the token password you retrieved in step 3 above
 
 !!! note "Authentication token validation delay"
diff --git a/docs/infrastructure_and_maintenance/security/reporting_issues.md b/docs/infrastructure_and_maintenance/security/reporting_issues.md
@@ -12,7 +12,7 @@ No engineering team is perfect though, and if you do discover a security issue i
 
 ## Channels
 
-- If you're a customer or partner, please log in to your Service Portal at <https://support.ibexa.co/>, click "New Ticket", and report the issue as you would report a normal support request. [[= product_name_base =]] Product Support will respond, take care of the report, and keep you informed of the developments.
+- If you're a customer or partner, please log in to your Service portal at <https://support.ibexa.co/>, click "New Ticket", and report the issue as you would report a normal support request. [[= product_name_base =]] Product Support will respond, take care of the report, and keep you informed of the developments.
 - If you're not a customer or partner, please log in to the [[= product_name_base =]] JIRA issue tracker: <https://issues.ibexa.co/>. Create an account if you don't have one, it's free. Click the "Create" button in the top menu to create your report. For "Project", select "[[= product_name_base =]] IBX", or "eZ Publish / Platform", or "eZ Platform Enterprise Edition", depending on which product is affected by the bug. **Important: Select "Security Level": "Security"!** The engineering team will take care of your report.
 - It's also possible to report security issues by email to <security@ibexa.co> - this requires no account.
 
diff --git a/docs/infrastructure_and_maintenance/security/security_checklist.md b/docs/infrastructure_and_maintenance/security/security_checklist.md
@@ -8,7 +8,7 @@ When getting ready to go live with your project for the first time, or when re-l
 
 !!! caution
 
-    Security is an ongoing process. After going live, you should pay attention to security advisories released via [your service portal](https://support.ibexa.co/), or via [Security advisories](https://developers.ibexa.co/security-advisories) if you're not a subscriber.
+    Security is an ongoing process. After going live, you should pay attention to security advisories released via [your Service portal](https://support.ibexa.co/), or via [Security advisories](https://developers.ibexa.co/security-advisories) if you're not a subscriber.
 
 ## [[= product_name =]]
 
diff --git a/docs/resources/contributing/report_and_follow_issues.md b/docs/resources/contributing/report_and_follow_issues.md
@@ -17,7 +17,7 @@ If you find any, update them with your comment or additional information instead
 
     If you discover a security issue, please don't report it through regular channels, but instead take a look at the [Security section](reporting_issues.md).
 
-If you have an [[= product_name =]] subscription, report your issues through the [support portal](https://support.ibexa.co) instead of JIRA.
+If you have an [[= product_name =]] subscription, report your issues through the [Service portal](https://support.ibexa.co) instead of JIRA.
 This ensures the issue can be quickly prioritized according to its impact.
 
 If you cannot find an existing ticket matching what your issue, you can create a new one.
diff --git a/docs/resources/release_process_and_roadmap.md b/docs/resources/release_process_and_roadmap.md
@@ -60,4 +60,4 @@ Distribution files of [[= product_name_base =]] three editions are as follows:
 [[= product_name_base =]]'s support and maintenance services specific to each release are only available from a given start date until an end date.
 The time in between the start and end dates is what [[= product_name_base =]] calls the product's **Service Life**.
 
-You can find the specific dates of service life for each release on [[= product_name_base =]] [support portal service life page](https://support.ibexa.co/Public/Service-Life).
+You can find the specific dates of service life for each release on [[= product_name_base =]] [service life page](https://support.ibexa.co/Public/Service-Life).
diff --git a/docs/snippets/update/notify_support.md b/docs/snippets/update/notify_support.md
@@ -1,6 +1,6 @@
 ## Notify support
 
-Please tell support that you have updated your installation.
-They update your support portal to match the new version.
+Inform the support team that you have updated your installation.
+They update your Service portal to match the new version.
 This ensures that you receive notifications about new maintenance releases and security advisories for the correct version.
-You can contact support at support@ibexa.co or through your [Support portal](https://support.ibexa.co).
+You can contact the support team at support@ibexa.co or through your [Service portal](https://support.ibexa.co).
diff --git a/docs/update_and_migration/from_4.6/update_from_4.6.md b/docs/update_and_migration/from_4.6/update_from_4.6.md
@@ -338,3 +338,24 @@ vendor/bin/rector --dry-run
 ``` bash
 vendor/bin/rector
 ```
+
+[[% include 'snippets/update/notify_support.md' %]]
+
+With the product updated to the latest version, you can now finish the update process or proceed to updating the LTS Updates packages.
+
+## LTS Updates
+
+[LTS Updates](editions.md#lts-updates) are standalone packages with their own update procedures.
+To use the [latest features](ibexa_dxp_v4.6.md) added to them, update them separately with the following commands:
+
+=== "AI actions"
+
+    ```bash
+    composer require ibexa/connector-ai:[[= latest_tag_4_6 =]] ibexa/connector-openai:[[= latest_tag_4_6 =]]
+    ```
+
+=== "Date and time attribute"
+
+    ```bash
+    composer require ibexa/product-catalog-date-time-attribute:[[= latest_tag_4_6 =]]
+    ```
