@taylorotwell, The idea was for third-party packages to use this tag too. But laravel-assets will not reflect content. Maybe change to vendor-assets?

May be add /public/vendor to .gitignore

This doesn't seem to be working for some reason. I didn't notice until today because I was expecting a change in the assets.

To replicate, create a new Laravel app and install an older version of Horizon and/or Telescope (I used Horizon for my test since there was a release today), then update to the latest version of either package:

laravel new asset-test && cd asset-test

composer require laravel/horizon:5.7.15

Assets were published automatically after Horizon was installed - yay! Now change the version requirement in composer.json to ^5.7 and update:

composer update

Assets were not published, even though they were changed in the new version of Horizon. The console says they were published, but nothing happened:

> @php artisan vendor:publish --tag=laravel-assets --ansi
Copied Directory [/vendor/laravel/horizon/public] To [/public/vendor/horizon]

So, let's run the same command:

php artisan vendor:publish --tag=laravel-assets

Nope, didn't work while running manually. Have to publish them from the package itself:

php artisan horizon:publish

Now they are updated... The output of the command is exactly the same as the vendor:publish one, so I don't know what is going on. Here's a sample repo: https://github.com/mikemand/laravel-asset-test Each commit is one of the steps above.

@mikemand it seems the vendor:publish command will not update the assets if they already exist.
On the other hand horizon:publish calls vendor:publish --force which will replace the existing assets.

So in my composer.json I modified the script like this:

{
    "post-update-cmd": [
        "@php artisan vendor:publish --tag=laravel-assets --ansi --force"
    ],
}

Now my assets are updated correctly.

Perfect, @sebdesign. With your permission, I'll PR this fix here.