[heliocosta-dev]

MillionSend v0.22.0 adds a third contact property type, date, next to string and number. It is a MillionSend extension, since Resend has only the two. This brings the docs in line; no code changes.

• ContactProperties docblock and README → Contact properties: the type is string, number or date. A date property's values and its fallback_value must read as a date, or the write answers 422 validation_error. What reads as a date:
  • YYYY-MM-DD, read as midnight UTC;
  • a date-time with T or a space, read as UTC when it names no zone;
  • Unix time in seconds or milliseconds between 2000-01-01 and 2100-01-01.
• README → Contact properties also says contacts->get() returns each property as ['type' => …, 'value' => …], with a date's stored text as its value, and adds a create() example with 'type' => 'date'.
• README → Segments: created_at and property:<key> take four date ops. before and after take an ISO date or date-time. in_last_days and not_in_last_days take a whole number of days as a string, from '1' to '36500'.
• README → compatibility notes: the date type is listed among the MillionSend extensions.
• Both README paragraphs end with what servers before v0.22.0 do.

Runtime behavior doesn't change. create()'s param shape types type as string, and responses are json_decode(…, true) arrays, so a "type": "date" reads like any other. It's docs only, so there's no version bump and nothing to tag.

Checked in php:8.4-cli the way CI does: composer install, Pest (94 passed, 2 E2E skipped), Pint and PHPStan level 8 (no errors).

🤖 Generated with Claude Code