mirror of
https://github.com/warmbly/warmbly.git
synced 2026-08-19 08:01:16 +00:00
79b87b9b19
the multiplier was a no-op since the default already sat at 1.0, and plan tiers / admin overrides express the actual ceiling more clearly as a fixed limit_*_pm value. enterprise customers who need more throughput now get a direct bump on user_rate_limits.limit_*_pm instead of an indirect multiplier. migration 43 drops the column from both tables. service.go uses the base limit as the ceiling. UpdateUserRateLimits no longer accepts a burst_multiplier field.