[7.x] Suggest asset publishing Composer hook

horizon.md

@@ -102,9 +102,19 @@ Horizon exposes a dashboard at `/horizon`. By default, you will only be able to
 
 When upgrading to a new major version of Horizon, it's important that you carefully review [the upgrade guide](https://github.com/laravel/horizon/blob/master/UPGRADE.md).
 
-In addition, you should re-publish Horizon's assets:
+In addition, when upgrading to any new Horizon version, you should re-publish Horizon's assets:
 
     php artisan horizon:publish
+
+To keep the assets up-to-date and avoid issues in future updates, we highly recommend adding the command to the `post-autoload-dump` scripts in your `composer.json` file:
+
+    {
+        "scripts": {
+            "post-update-cmd": [
+                "@php artisan horizon:publish --ansi"
+            ]
+        }
+    }
 
 <a name="running-horizon"></a>
 ## Running Horizon

telescope.md

@@ -5,7 +5,8 @@
     - [Configuration](#configuration)
     - [Data Pruning](#data-pruning)
     - [Migration Customization](#migration-customization)
-- [Dashboard Authorization](#dashboard-authorization)
+    - [Dashboard Authorization](#dashboard-authorization)
+- [Upgrading Telescope](#upgrading-telescope)
 - [Filtering](#filtering)
     - [Entries](#filtering-entries)
     - [Batches](#filtering-batches)
@@ -50,12 +51,6 @@ After installing Telescope, publish its assets using the `telescope:install` Art
 
     php artisan migrate
 
-#### Updating Telescope
-
-When updating Telescope, you should re-publish Telescope's assets:
-
-    php artisan telescope:publish
-
 ### Installing Only In Specific Environments
 
 If you plan to only use Telescope to assist your local development, you may install Telescope using the `--dev` flag:
@@ -113,7 +108,7 @@ By default, all entries older than 24 hours will be pruned. You may use the `hou
     $schedule->command('telescope:prune --hours=48')->daily();
 
 <a name="dashboard-authorization"></a>
-## Dashboard Authorization
+### Dashboard Authorization
 
 Telescope exposes a dashboard at `/telescope`. By default, you will only be able to access this dashboard in the `local` environment. Within your `app/Providers/TelescopeServiceProvider.php` file, there is a `gate` method. This authorization gate controls access to Telescope in **non-local** environments. You are free to modify this gate as needed to restrict access to your Telescope installation:
 
@@ -134,6 +129,23 @@ Telescope exposes a dashboard at `/telescope`. By default, you will only be able
     }
 
 > {note} You should ensure you change your `APP_ENV` environment variable to `production` in your production environment. Otherwise, your Telescope installation will be publicly available.
+
+<a name="upgrading-telescope"></a>
+## Upgrading Telescope
+
+When upgrading to a new version of Telescope, you should re-publish Telescope's assets:
+
+    php artisan telescope:publish
+
+To keep the assets up-to-date and avoid issues in future updates, we highly recommend adding the command to the `post-autoload-dump` scripts in your `composer.json` file:
+
+    {
+        "scripts": {
+            "post-update-cmd": [
+                "@php artisan telescope:publish --ansi"
+            ]
+        }
+    }
 
 <a name="filtering"></a>
 ## Filtering