Upgrade from 1.x

LaraPost 2.x is a deliberate major release. It narrows the supported framework baseline and changes security defaults before adding TikTok, queue hardening, and optional MCP.

Why this is 2.0

• PHP 8.3+ replaces the PHP 8.2 baseline.
• Laravel 12 and 13 are supported; Laravel 11 moved out of its security support window.
• The operator dashboard is authenticated by default.
• OAuth state validation is stricter.

1. Update Composer requirements

composer require prateekbhujel/larapost:^2.0 -W

2. Republish and compare config

php artisan vendor:publish --tag=larapost-config --force

If you maintain custom config changes, compare before overwriting. The important additions are enabled_platforms, scheduler settings, separate operator/callback middleware, and optional MCP settings.

3. Choose enabled platforms

LARAPOST_PLATFORMS=facebook,twitter,linkedin,tiktok

You can omit providers you do not use.

4. Review dashboard authorization

The v2 default is ['web', 'auth']. If your app uses a custom guard, tenant middleware, or admin authorization layer, configure operator_middleware explicitly rather than making the dashboard public.

5. MCP is opt-in

Existing publishing installations do not need laravel/mcp. Install it only if you want the remote AI integration:

composer require laravel/mcp:^1.0
php artisan larapost:install --mcp

6. Verify

php artisan migrate
php artisan larapost:doctor
php artisan test

1.x backports

The 1.x branch is reserved for critical fixes that still apply to the original release line. New features belong on main.