Hostney Migration

1.0.5

• Security: the migration token is deleted from your site when the migration is over.
  Hostney now tells the plugin to disconnect when a migration completes, fails for
  good or is cancelled, and when its token is revoked or expires. Until now the token
  stayed in your site’s settings until you clicked Disconnect or deactivated the plugin.
• Security: a connection now ends on its own 7 days after you connected, even if
  Hostney cannot reach your site to disconnect it.
• Security: the plugin’s REST API endpoints now exist only while a token is stored.
• Security: the file reader’s check that a file sits inside your WordPress folder no
  longer accepts a neighbouring folder whose name starts the same way.
• Fixed: failed sign-in attempts by other visitors behind the same proxy (Cloudflare,
  for example) could pause a running migration for up to a minute. A correctly signed
  request is never held back by someone else’s failures now.
• Fixed: every request was counted twice against the rate limit, and every failed
  sign-in twice against the lockout, because WordPress checks a route’s permissions a
  second time after answering it. The limit of 900 requests a minute was really 450,
  which a migration could reach and then have to wait out.
• Changed: when Hostney asks for it, database tables are exported in key order, one
  page strictly after the last. Rows added or removed on a busy site during the
  migration can no longer shift the pages, and tables whose primary key has more than
  one column are no longer split part-way through a key.

1.0.4

• Added: the system requirements panel now reports the size of your database.
• Changed: a site whose database is larger than the destination hosting plan allows
  is now told so when it connects, instead of partway through the migration. Nothing
  is copied in that case, and reconnecting works once the plan is upgraded or the
  database is reduced.

1.0.3

• Fixed: the per-IP rate limiter refreshed its own expiry on every request, so the
  60-second window never elapsed during a migration and the limit behaved as a
  one-time cap of 900 requests. Large sites were rejected with HTTP 429 partway
  through the database export.
• Added: a Retry-After header on rate-limited responses, so the caller knows exactly
  how long to wait instead of guessing.
• Changed: the request rate limit now applies only to authenticated requests.
  Unauthenticated traffic is handled by a separate failed-authentication throttle and
  can no longer consume a running migration’s request budget.

1.0.2

• Confirmed compatibility with WordPress 7.1

1.0.1

• Confirmed compatibility with WordPress 7.0

1.0.0

• Initial release
• Database export with primary key pagination and adaptive batch sizing
• Filesystem export with chunked transfers and MD5 checksum verification
• HMAC-SHA256 authentication with timestamp validation
• WAF-compatible base64 encoding for request and response bodies
• Path traversal protection with realpath validation
• Admin UI with system requirement checks