opensource/filament
3
0
Fork 0
mirror of https://github.com/filamentphp/filament.git synced 2026-09-24 15:42:09 +08:00
Code Issues Packages Projects Releases Wiki Activity

wip

Browse Source
This commit is contained in:
Dan Harrin
2023-08-31 13:20:50 +03:00
parent 41388e3ac3
commit dbb5d0bc62
5 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
packages/actions/docs/10-upgrade-guide.md
+1 -1
View File
@@ -34,7 +34,7 @@ You can now `composer remove filament/upgrade` as you don't need it anymore.
## Upgrading manually
After upgrading the dependency via Composer, you should execute `php artisan filament:upgrade` in order to clear any caches and publish the new assets.
After upgrading the dependency via Composer, you should execute `php artisan filament:upgrade` in order to clear any Laravel caches and publish the new frontend assets.
### Low-impact changes
packages/forms/docs/10-upgrade-guide.md
+1 -1
View File
@@ -33,7 +33,7 @@ You can now `composer remove filament/upgrade` as you don't need it anymore.
## Upgrading manually
After upgrading the dependency via Composer, you should execute `php artisan filament:upgrade` in order to clear any caches and publish the new assets.
After upgrading the dependency via Composer, you should execute `php artisan filament:upgrade` in order to clear any Laravel caches and publish the new frontend assets.
### High-impact changes
packages/notifications/docs/07-upgrade-guide.md
+1 -1
View File
@@ -33,7 +33,7 @@ You can now `composer remove filament/upgrade` as you don't need it anymore.
## Upgrading manually
After upgrading the dependency via Composer, you should execute `php artisan filament:upgrade` in order to clear any caches and publish the new assets.
After upgrading the dependency via Composer, you should execute `php artisan filament:upgrade` in order to clear any Laravel caches and publish the new frontend assets.
### High-impact changes
packages/panels/docs/14-upgrade-guide.md
+1 -1
View File
@@ -36,7 +36,7 @@ You can now `composer remove filament/upgrade` as you don't need it anymore.
## Upgrading manually
After upgrading the dependency via Composer, you should execute `php artisan filament:upgrade` in order to clear any caches and publish the new assets.
After upgrading the dependency via Composer, you should execute `php artisan filament:upgrade` in order to clear any Laravel caches and publish the new frontend assets.
### High-impact changes
packages/tables/docs/13-upgrade-guide.md
+1 -1
View File
@@ -33,7 +33,7 @@ You can now `composer remove filament/upgrade` as you don't need it anymore.
## Upgrading manually
After upgrading the dependency via Composer, you should execute `php artisan filament:upgrade` in order to clear any caches and publish the new assets.
After upgrading the dependency via Composer, you should execute `php artisan filament:upgrade` in order to clear any Laravel caches and publish the new frontend assets.
### High-impact changes