v0.8.0 — Aether Rename

Renames the Composer package and the PHP namespace to the aether names.

Breaking change — A Composer consumer changes its requirement from uams-web/uamswp-migration-api to uams-web/aether-wordpress-migration-api and its use statements from UAMSWP\MigrationAPI to UAMSWeb\Aether\WordPressImporter\MigrationApi. No route, field or response shape changes, so wordpress-importer reading the API over HTTP changes nothing. A WordPress site deployed with WP Pusher keeps pointing at the old repository name, which GitHub redirects, and keeps its plugin folder uamswp-migration-api; the plugin file, text domain and REST namespace are unchanged.

Marked pre-release. Nothing pins this repository: wordpress-importer reads it over HTTP rather than as a package.

Breaking changes

• Rename the Composer package and PHP namespace to aether-wordpress-migration-api #44

Maintenance and tooling

• Bump the plugin version to 0.8.0 #45
• Build(deps-dev): Bump the composer-minor-and-patch group with 4 updates #43
• Build(deps-dev): Bump the composer-integration-minor-and-patch group in /tests/Integration with 2 updates #42
• Raise the development PHP pin from 8.4.1 to 8.4.27 #40

Verification at this tag

The remote GitHub Actions chain passed on the validated head a0f9b94d0 of #45. All 30 check runs concluded success, which covers every chained job on both ubuntu-latest and windows-latest. The tagged commit is the squash merge 2401dc2df. Its tree is identical to the validated head: git diff --quiet exits 0 against it. #44, the rename itself, passed all 30 check runs on its head 220469181 before it merged as 6be1f5b53.

Known gaps

Carried in docs/known-gaps.md rather than repeated here.