v0.1.7

Changes

• The verification flow now exposes the expiry timestamp as the raw UTC database value; message templates remain responsible for localized formatting.

Validation

• PHP 8.1 and PHP 8.4 CI passed
• The installable ZIP was built directly from v0.1.7 and verified

CiviVerify 0.1.6

CiviVerify 0.1.6 adds optional explicit selection of an active, non-reserved CiviCRM message template for CiviVerifyToken.issueAndSend, while retaining the required workflow context.

CiviVerify 0.1.5

Security

• Limit each six-digit verification code to five failed attempts.
• Revoke the whole verification transaction at the limit and enqueue the standard revocation event.

CiviVerify 0.1.4

Changed

• Add six-digit alternate verification codes alongside confirmation links.
• Verify codes atomically using the issued UUID and a separately keyed digest.
• Add email template token support, migrations, documentation, translations, and regression coverage.

CiviVerify 0.1.3

Changed

• CiviVerifyToken.issueAndSend can select an existing administrator-configured confirmation target by targetKey.
• Callers cannot supply routes or URLs.

CiviVerify 0.1.2

Changed

• German verification emails now show expiry timestamps as localized, minute-precise dates and times.

CiviVerify 0.1.1

Fixes an API4 metadata authorization error when opening SearchKit administration. Outbox metadata is available to CiviCRM users, while access to Outbox records remains restricted to verification-token administrators.

CiviVerify 0.1.0

First stable CiviVerify release for the CiviCRM Extensions Directory. Provides generic, single-use, time-limited verification links with lifecycle events, optional CiviRules integration, scanner-safe confirmation, and a scheduled cleanup and event-delivery workflow.

CiviVerify 0.1.0-beta.6

Completes API3 compatibility for CiviVerify managed jobs. The cleanup and outbox jobs now invoke shared services through API3 bridges; retention_days=0 retains the configured cleanup default.

CiviVerify 0.1.0-beta.5

Corrects the release-archive installation instructions. The README now uses one explicit version variable for the archive name and GitHub release URL.