log/ Changelog
Every change, dated.
New features, fixes and breaking changes across the API, SDKs, dashboard and portal. Breaking changes only ever arrive with a new API version.
Current API version
2026-09-01
October 2026
-
v4.2.0
Feature
Replay by filter
Replay every event that matches a filter instead of one at a time: by endpoint, status code, event type and time range. Available in the dashboard, the CLI and the API.
forge replay --endpoint ep_7Hc2Qm --status 5xx --since 2h -
v4.1.4
Improvement
Faster delivery log search
Searching delivery logs by payload content is now up to 9× faster on large projects, and results stream in as they are found.
-
dashboard
Fix
Fixed timezone in delivery charts
Delivery charts showed hours in UTC even when your profile was set to a local timezone. They now follow your profile setting, with UTC shown on hover.
September 2026
-
v4.1.2
Fix
Go SDK: context cancellation on retries
The Go SDK now stops retrying as soon as the request context is cancelled, instead of finishing the backoff schedule.
-
API 2026-09-01
BreakingFeature
New API version: unified error objects
All errors now share one shape with
type,code,messageandparam. The old top-levelerror_messagefield is removed in this version. Keys pinned to2026-03-15are unaffected until you upgrade.- { "error_message": "limit must be between 1 and 100" } + { "error": { "type": "invalid_request_error", "param": "limit", + "message": "limit must be between 1 and 100" } } -
v4.0.0
Breaking
SDKs 4.0 for API 2026-09-01
Every official SDK has a 4.0 release that targets the new API version. Errors are raised as typed exceptions per
type. See the quickstart for updated examples.
August 2026
-
v3.9.0
Feature
Per-endpoint rate limits
Set a maximum requests per second on any endpoint. Bursts above the limit are queued and smoothed instead of failing, and the portal shows customers their current limit.
-
portal
Improvement
Portal: secret rotation with overlap
Customers can rotate their signing secret from the portal. The old secret stays valid for 24 hours so their deploy never drops a request.
-
v3.8.3
Fix
Idempotency keys longer than 64 characters
Idempotency keys up to 255 characters are now accepted. Previously keys over 64 characters were silently truncated, which could merge unrelated events.
July 2026
-
v3.8.0
Feature
Singapore region
ap-southeastis generally available. Events, logs and secrets for projects in the region never leave Singapore. -
v3.7.1
Improvement
Retry schedule now ends at 72 hours
The final retry moved from 48 to 72 hours after the first attempt, so a weekend outage on a customer’s side no longer loses events.
-
API 2026-03-15
Breaking
TLS 1.0 and 1.1 removed for endpoints
Forge no longer delivers to endpoints that only support TLS 1.0 or 1.1. Affected endpoint owners were emailed three times since April.
No entries of this type yet.
Never miss a breaking change.
Subscribe in the footer, or watch the Forge-Deprecation response header.