Skip to main content
Version: 1.x

Upgrade guide

The documentation currently covers the 1.x release line. Review the package release notes and your dependency lock before each update.

Before upgrading​

  1. Confirm that the target version supports the application's PHP and Laravel versions.
  2. Commit composer.lock and the current published config/feeds.php.
  3. Record active feed registrations and generated-file destinations.
  4. Run the application's feed generation tests or generate representative feeds in a non-production environment.

Apply the update​

composer update dragon-code/laravel-feeds --with-all-dependencies

For an existing installation, copy only database/migrations/2026_10_14_000000_add_slug_to_feeds_table.php from the package into your application's migrations directory. Choose a filename timestamp immediately after the application's actual create_feeds_table migration and before any feed-registration migrations; keep the add_slug_to_feeds_table suffix. Then run php artisan migrate. The migration uses the configured connection and table and fills slugs from existing titles, including soft-deleted records. Do not republish or rerun the original create-table migration. Replace numeric feed IDs in commands and manual schedules with the stored slugs.

php artisan migrate

Compare the installed package's config/feeds.php with the application's published copy and merge new keys manually. Do not republish with --force: it overwrites application-specific values.

Verify​

  • Generate one feed for every used format.
  • Verify split-file counts and filenames.
  • Confirm scheduled and queued generation.
  • Confirm custom feed models, transformers, macros, and preset subclasses.
  • Compare representative output with the previous version.

Rollback​

Restore the previous composer.lock and configuration, run composer install, and apply the application's migration rollback policy. Generated files are deployment artifacts; restore or regenerate them according to the storage recovery plan.

See Also​