Acorn v4.0.0-beta.0 released

[QWp6t]

acorn v4.0.0-beta.0 released

What’s Changed

• Laravel v10 by @QWp6t in ⬆️ Laravel v10 by QWp6t · Pull Request #299 · roots/acorn · GitHub
• Exit parse_request to short circuit wordpress during custom routes. by @eavonius in https://github.com/roots/acorn/pull/301
• ‘enqueueJs()’ support to registering scripts with async and defer by @ouun in https://github.com/roots/acorn/pull/313

New Contributors

• @eavonius made their first contribution in https://github.com/roots/acorn/pull/301
• @szepeviktor made their first contribution in https://github.com/roots/acorn/pull/312

Full Changelog: https://github.com/roots/acorn/compare/v3.2.0...v4.0.0-beta.0

[Log1x]

Upgrading to Acorn 4.x

Step 1. Upgrade Acorn

$ composer remove roots/acorn
$ composer upgrade
$ composer require roots/acorn:v4.0.0-beta.0 -W

Step 2. Upgrade Packages

All of my packages other than ACF Composer have a release and should bump with composer upgrade. For ACF Composer, you should be able to safely use log1x/acf-composer:dev-master for now.

Step 3. Update Parent Namespace in Service Providers

All service providers used inside of your application or packages should now extend Illuminate:

- use Roots\Acorn\ServiceProvider;
+ use Illuminate\Support\ServiceProvider;

Step 4. Update Acorn Configs (If Applicable)

If you previously published Acorn’s config(s), you can delete them all and re-publish/re-modify them with your changes or grab them manually from the Acorn repo. You mainly need the new provider stuff if you published config/app.php.

If any packages/dependencies have conflicts while updating, try removing and then re-requiring them after Acorn is bumped to 4.x.