@buildbase/sdk 0.0.75 → 0.0.76

package/CHANGELOG.md

@@ -7,6 +7,34 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.0.76] - 2026-10-02
+
+### Fixed
+
+- **The same read is no longer sent once per mounted hook.** `useSubscription`,
+  `useAllQuotaUsage` and `useCreditBalance` each keep their own state, which is
+  what lets a header badge and a settings screen show the same number without
+  one owning the other. They also each sent their own request: an app with the
+  context provider plus two direct callers made three identical GETs on mount,
+  and three more on every `invalidate*()` - which the membership writes call on
+  every add, remove and invitation. A request already in flight for the same
+  server, org and workspace is now shared by everyone who asks for it.
+
+  It is not a cache: the entry lives exactly as long as the request, so a later
+  mount still reads fresh and an invalidation is still a real refetch. Only the
+  duplicate already on the wire is removed.
+
+- **An inline `auth` prop no longer re-dispatches the whole config on every
+  render.** `ContextConfigProvider` depended on `auth.callbacks` by identity,
+  and `auth={{ clientId, redirectUrl, callbacks: { ... } }}` - what the docs
+  show and what most apps write - is a new object each render. So the OS config
+  was re-dispatched, the reducer returned new state, and every `useSaaSOs()`
+  consumer re-rendered: the workspace actions, the auth hooks, and each data
+  hook that builds an api from the config. The callbacks now sit behind a
+  forwarder whose identity is stable and which always calls the current
+  implementation. Callbacks the app did not pass stay absent, because several
+  call sites ask whether one was supplied at all.
+
 ## [0.0.75] - 2026-10-02
 
 ### Fixed