mailblastr 3.0.1 → 4.0.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: d9de7ff5dac71bd3ba5db1b38369328167f9b2a52b59974201f868299f23d35c
4
- data.tar.gz: bc48385e4675d1c6ef5163e5fb7a2583b145562bf43e8a4d5d3d33f9797eecea
3
+ metadata.gz: af406b751cac271f65de584e43a1b405887cbfa13448eace04d4ba8a58f57567
4
+ data.tar.gz: 46c015562325cd114404e4f34e17ac44b7481ae781bb013aba951349fe016fc9
5
5
  SHA512:
6
- metadata.gz: 40472dc57967817c0071973ecb6d7f353f5a927f9261c76f035f13552d47680481caad49fcf01da8a6698996278811f23c6a8b999a6aa8312461e92d88676a0e
7
- data.tar.gz: 63131860cae2becb8dddc98c36aed13e970433541b81e4c0b93732ca968ab9a7a2db9c6ee7d5630d114a2e46ea3d09c21d7a49193f7e337b98dce95bf42c7057
6
+ metadata.gz: b65ef435e4c88cc4415eba880b0be79ae107f7f20d374e6f30a4b19e7c85b5afb4c49833910a671979150407659b13e39a097d84cef3174a168cae3d0514b835
7
+ data.tar.gz: 157b75d0c9c47f2d0a78561238ab61ce03779ddf8da3b2a1a633cca472cfe0a66a2f392f2da54554aa2fa1dac319adac0ceddc03f313c871fde79dcd6dcd394c
data/README.md CHANGED
@@ -402,7 +402,7 @@ Only `Emails.send` and `Batch.send` honour the header. Every other endpoint —
402
402
 
403
403
  ## Rate limits
404
404
 
405
- Only the `/emails` routes are rate-limited: **30 requests per minute per IP**, covering reads as well as sends. Those responses carry `RateLimit-Limit`, `RateLimit-Remaining` and `RateLimit-Reset` headers (on successes too) so you can throttle before being rejected. The SDK retries a 429 or 503 automatically — up to `Mailblastr.max_retries` times (default 2), honouring `Retry-After`.
405
+ Only the `/emails` **send** routes are rate-limited: **30 requests per minute per IP**. Reads (`GET /emails`, `GET /emails/:id`, the `receiving` subtree and attachment listings) are NOT subject to that cap, so paging a large list no longer risks a 429. Capped responses carry `RateLimit-Limit`, `RateLimit-Remaining` and `RateLimit-Reset` headers (on successes too) so you can throttle before being rejected. The SDK retries a 429 or 503 automatically — up to `Mailblastr.max_retries` times (default 2), honouring `Retry-After`.
406
406
 
407
407
  ## Documentation
408
408
 
@@ -1,5 +1,5 @@
1
1
  # frozen_string_literal: true
2
2
 
3
3
  module Mailblastr
4
- VERSION = "3.0.1"
4
+ VERSION = "4.0.0"
5
5
  end
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: mailblastr
3
3
  version: !ruby/object:Gem::Version
4
- version: 3.0.1
4
+ version: 4.0.0
5
5
  platform: ruby
6
6
  authors:
7
7
  - MailBlastr
8
8
  autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
- date: 2026-08-14 00:00:00.000000000 Z
11
+ date: 2026-08-19 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: minitest