v1.1.2

New Features

• None.

Improvements

• Queued delivery payloads are stored in randomized, non-autoloaded options instead of transients, so they survive an object cache flush between the moment an event is queued and the moment WP-Cron delivers it. Only the opaque ticket is still passed as a cron argument, so member data stays out of the autoloaded cron option.
• A daily cleanup event removes payloads whose delivery never ran, which options need because they do not expire on their own.
• Payloads are kept for three days rather than six hours. WP-Cron only runs on visitor requests, and on a low-traffic site six hours could elapse before anything triggered the queue.
• Debug logging now records when a delivery is queued and when it is sent, and every drop path reports the method and target. An empty log previously could not distinguish an event hook that never fired from a payload that was queued and then lost.

Bug Fixes

• Fixed queued notifications being silently dropped when a persistent object cache was flushed after the event was scheduled. The cron entry survived in the database while the payload did not, so the delivery ran with nothing to send.
• Fixed the pacing and retry paths deleting the payload of a delivery that was still scheduled. Those paths reuse the same ticket, and WordPress refuses to schedule a duplicate hook and argument pair within ten minutes, so a concurrent cron spawn could strand a live event.

Compatibility

• No settings or data changes. Deliveries queued by earlier versions are still resolved from their transients and are processed without migration.
• Background delivery still depends on WP-Cron. On a site with little traffic, configure a system cron to request wp-cron.php and set DISABLE_WP_CRON so notifications do not wait for the next visitor.

v1.1.1

New Features

• None.

Improvements

• ARMember is now declared as a required plugin through the Requires Plugins header. WordPress blocks TelegrARM activation until ARMember is installed and active, and prevents ARMember from being deactivated while TelegrARM is running.

Bug Fixes

• None.

Compatibility

• The header resolves the wordpress.org slug armember-membership. That listing was closed on 2025-02-01 and ARMember is no longer downloadable from wordpress.org, so the dependency can only be satisfied by an existing armember-membership plugin folder. Sites that already run ARMember Lite are unaffected and activate normally. New installs, and sites running ARMember Premium from CodeCanyon (which has no wordpress.org slug), cannot satisfy the dependency and will not be able to activate TelegrARM.

v1.1.0

New Features

• None.

Improvements

• WordPress 7.0 is now the minimum supported version, and the plugin is tested against WordPress 7.0.3. Sites running an older WordPress will not be offered the update.
• Removed the runtime PHP version guard and its admin notice. The Requires PHP: 8.0 plugin header is enforced by WordPress core at install, update, and activation, so the in-plugin check was redundant. PHP 8.0 remains the minimum, and CI still covers PHP 8.0, 8.2, and 8.5.

Bug Fixes

• None.

v1.0.1

New Features

• None.

Improvements

• Member data is no longer stored in the autoloaded cron option. Queued Telegram deliveries now keep their payload in a randomized, non-autoloaded transient and pass only an opaque ticket as the cron argument, so phone numbers, names, and message bodies are not loaded on every request and are not displayed by cron-inspection plugins. Payloads are deleted on success, on abandonment after the retry cap, on non-retryable rejection, and on uninstall. Events queued by 1.0.0 are still accepted, so no migration is required.
• Per-chat pacing now enforces a real interval. The previous comparison only deferred deliveries queued within the same second; the queue now spaces messages to one every four seconds per chat, roughly 15 per minute, staying under Telegram's per-group limit.
• The Telegram bot token settings sanitizer only inspects the clear-token checkbox inside a nonce-verified settings save, so an unrelated option update in an admin request can no longer blank the stored credential.
• Uninstall removes queued delivery payloads, pacing markers, and dedupe markers in addition to plugin options.
• Releases now publish explicit notes from release-notes/<version>.md, along with a SHA-256 checksum and a GitHub build provenance attestation for the plugin ZIP.

Bug Fixes

• Sending an admin test message with a malformed bot token now reports the format error instead of silently testing the previously saved token and reporting success.

v1.0.0

What's Changed

• build(deps): bump softprops/action-gh-release from 2 to 3 by @dependabot[bot] in #5
• build(deps): bump actions/checkout from 6 to 7 by @dependabot[bot] in #6

Full Changelog: v0.5.4...v1.0.0

v0.5.4

Full Changelog: v0.5.3...v0.5.4

v0.5.3

Full Changelog: v0.5.2...v0.5.3

v0.5.2

Full Changelog: v0.5.1...v0.5.2

v0.5.1

Full Changelog: v0.5.0...v0.5.1

v0.5.0

Full Changelog: v0.4.4...v0.5.0