Release v0.2.0 · WordPress/abilities-api

What's Changed

Refactor the usage of $properties param to $args to align with WordPress usage by @gziolo in #59
Add HEAD method support for performance optimization by @Ref34t in #71
Fix $input type hint in WP_Ability by @gziolo in #61
chore: update dev-deps to latest by @justlevine in #72
fix: use link_header instead of add_link for pagination responses by @emdashcodes in #81
Update CONTRIBUTING.md by @akkspros in #80
Docs: REST API Reference by @gziolo in #77
Add execute actions to the ability object by @gziolo in #56
dev: Bump the PHPStan testing to PHP 8.4 by @johnbillion in #82
feat!: make permission_callback arg required by @justlevine in #73
Add client-side package for Abilities API by @emdashcodes in #60
dev: add register_ability_args filter [Proposal] by @justlevine in #74
docs: Fix the variable name by @mrabbani in #92
Fix has_permission() return type inconsistency (Issue #67) by @Ref34t in #76
Docs/semantic headings by @jonathanbossenger in #96
Rename check_permission() to check_permissions() on WP_Ability by @gziolo in #94
Fix backwards compatibility with WP_REST_Request API by @budzanowski in #98
Prepare the branch for v0.2.0 release by @gziolo in #90
Include JS build files in the Composer package in v0.2.0 release by @gziolo in #100

They are primarily included in the WP_Ability object:

permission_callback is now mandatory when registering an ability with wp_register_ability.
has_permission was deprecated in favor of check_permissions.
execute and check_permissions (previously has_permission) methods no longer accept only arrays. It's now possible to provide any input type, and it defaults to null.
When no input schema is provided, then permission_callback and execute_callback get executed with no arguments.
Some other protected methods, like validate_input and do_execute, also have different method signatures because of the input parameter changes.

Full Changelog: v0.1.1...v0.2.0-rc