Bug fix

Fixes a bug mentioned in #55

Policy updates

The current standardised policies have been amended, according to the W3C docs.

Also a new list of proposed policies have been added, which need to be enabled via the config in order to use them.

W3C docs

What's Changed

• update standardised permission policies by @Treggats in #26
• introduced proposed permission policies by @Treggats in #27
• PHPUnit upgrade to version 10 by @Treggats in #22
• a lot of under the hood changes

Full Changelog: v2.0...v2.1

Laravel 10 Support

• Add Laravel 10 support, thanks to @Treggats

What's Changed

• update phpunit config by @Treggats in #11
• added automated QA checks by @Treggats in #13
• clean up / refactor tests by @Treggats in #14
• [Laravel 10] update composer constraints by @Treggats in #15

New Contributors

• @Treggats made their first contribution in #11

Laravel 9 Support

• Add PHP 8.1 support
• Add Laravel 9 support

RFC-8941 support

Thanks to @MauricioKruijer

PHP 8 Support

• add PHP 8 support
• update dependencies

Forgot to fix the tests

Well, yeah. Fixed it.

Feature-Policy has been renamed to Permissions-Policy

From https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Feature-Policy

This header is still in an experimental state, and is subject to change at any time. Be wary of this when implementing it on your website. The header has now been renamed to Permissions-Policy in the spec, and this article will eventually be updated to reflect that change.

Laravel 8 support

Add Laravel 8 support.

Laravel 7 support

Thanks to @sander3 LFP is now available for Laravel 7.