See the storage you use, plus security and sign-in fixes
You can see every stored file counted against your storage allowance. Image URLs are capped, rate-limited answers say when to retry, and fixes reach security, sign-up, workflows, push, the audience, the console and self-hosting.
Added
2- BillingYou can see how much storage you use against your allowance, because every stored file is counted. The Storage card on the billing page and the meter in Assets show the bytes you store, in GB-months. One GB-month is 1 GB kept for a whole month.
- ConsoleBefore you delete an image or make it private, the console lists where it is used.
Improved
6- PlatformBehaviour change: an image URL field takes at most 2048 characters, and a longer one is refused with 400.
- PlatformWhen you send too many requests, the answer says when to try again: a 429 answer carries the reason rate_limited and retryAfter.
- PlatformA request with an unknown ?org= answers 404 (not found) instead of 500.
- AuthenticationBehaviour change: when your app has no Email and password method, people cannot sign up with a password. /register refuses it with 403 method_unavailable.
- ConsoleLong selects can be searched, and the Devices tab asks before ending a session. Menu names are in sentence case, and 24 more audit log actions have labels.
- SDKThe plan and credit pickers open on the visitor's currency, which is a behaviour change. 28 more countries have a currency, and Plan & Billing shows no N/A price while it loads. These came in @buildbase/sdk 0.0.84 to 0.0.88.
Fixed
10- SecurityAn audience import's status can be read only by its own organization. The organization export hides password hashes, session ids, tokens and secrets.
- SecurityRequests sent at the same time can no longer reuse a reset code or get past the five-try limit.
- SecurityRedirect URLs that start with javascript: or data: are refused. Code requests take the same time to answer whether or not an account exists, so the timing gives nothing away.
- PlatformA badly formed request now gets a 400 answer. That includes one the sanitiser (the input cleaner) cannot read, and one whose whole shape breaks a schema rule. Before, these passed through or failed with a 500 or 503.
- PlatformBusy servers no longer fail requests by closing database connections that are still in use.
- AuthenticationA failed sign-up no longer locks its address out, and the browser that signs up appears under Devices. The password and magic link method routes refuse another method's id.
- WorkflowsA Wait for event step resumes again after a server restart.
- NotificationsA push retries only the devices that failed briefly, and a push campaign sent right after you turn push off no longer goes out.
- AudienceAudience migrate reports the records it could not move, and collection versions get unique numbers.
- Self-hostingThe compose file passes TRUST_PROXY, and the generated compose gives the server 180 seconds to stop. Installation routes act only on organizations the caller runs.