@koolbase/js 11.0.0 → 11.2.0

package/CHANGELOG.md

@@ -7,6 +7,87 @@ is based on [Keep a Changelog][kac], and this project adheres to
 [kac]: https://keepachangelog.com/en/1.1.0/
 [semver]: https://semver.org/
 
+## 11.2.0
+
+### Fixed
+
+- **A function that timed out was indistinguishable from one that threw.** A
+  504 fell into the generic 5xx branch and arrived as
+  `FunctionExecutionError`. Those need different answers — a timeout means
+  retry, raise the function's timeout at deploy, or move the slow part
+  elsewhere; an exception means fix the code. The server has always told them
+  apart. Now `FunctionTimeoutError`, and 429 gets `FunctionRateLimitError`
+  rather than falling through untyped.
+
+- **`upload_expired` and `cap_below_usage` were unmapped in storage.** The
+  first matters: a presigned upload URL has a lifetime, and a user who picks a
+  file, gets distracted and confirms twenty minutes later hit it as a generic
+  failure. It is a retry, not a failure — presign again and send the same
+  bytes. Now `KoolbaseUploadExpiredError`.
+
+- **Four database codes were unmapped**: `ambiguous_match`,
+  `constraint_exists`, `constraint_not_found`, `insufficient_authority`. The
+  first is the one an app hits — an upsert whose filter matched more than one
+  record is refused rather than resolved, because picking one would be a
+  silent guess about which row the caller meant.
+
+- **Errors report the code the server sent, not their category.**
+  `KoolbaseNotFoundError` and `KoolbaseValidationError` each hardcoded one
+  code while being used for several, so a `collection_not_found` response
+  produced an error reporting `not_found`. Catching the class works as
+  before; reading `e.code` now gives the server's answer.
+
+### Why these were missing
+
+The API writes error codes through four different helpers, so no single
+search finds them all — which is how twenty-two codes across four surfaces
+went unmapped without anyone noticing. Each surface now has a test asserting
+every known code maps to its own class, so a new one added without a case
+here fails the build rather than a user's upload.
+
+## 11.1.0
+
+### Fixed
+
+- **Fourteen error codes the API emits were not mapped**, so they arrived as
+  a generic error and an app's `instanceof` branch silently never ran. The
+  most consequential is `contact_not_verified` — in a project with verified
+  contact required, a user who registers, does not click the link, and comes
+  back is the *commonest* auth failure there is, and it had no type. Now:
+
+  | Code | Class |
+  |---|---|
+  | `contact_not_verified`, `email_not_verified` | `ContactNotVerifiedError` |
+  | `signups_disabled` | `SignupsDisabledError` |
+  | `weak_password` | `WeakPasswordError` (existed, never mapped from the server) |
+  | `account_exists` | `AccountExistsError` |
+  | `token_expired` | `TokenExpiredError` |
+  | `token_used` | `TokenAlreadyUsedError` |
+  | `invalid_token` | `UnlockTokenInvalidError` |
+  | `invalid_password` | `CurrentPasswordIncorrectError` |
+  | `oauth_only_account` | `OAuthOnlyAccountError` |
+  | `unsupported_oauth_provider` | `UnsupportedOAuthProviderError` |
+  | `session_required` | `SessionRequiredError` |
+  | `insufficient_authority` | `InsufficientAuthorityError` |
+  | `last_credential` | `LastCredentialError` |
+  | `hide_requires_verification` | `HideRequiresVerificationError` |
+
+  `CurrentPasswordIncorrectError` is named for the operation rather than the
+  code: the server calls it `invalid_password`, which reads like a rejected
+  new password and means the opposite.
+
+- **`WeakPasswordError` carries the server's message** when there is one. The
+  SDK checks length before sending; a project may require more, and "must be
+  at least 8 characters" would then be both wrong and unhelpful. Its
+  constructor argument is optional, so existing code is unaffected.
+
+### Why these were missing
+
+Nothing inside the SDK can tell that a code fell through — the generic error
+is a valid object and the app's branch simply does not run. There is now a
+test that asserts every code maps to its own class, so a new code added to the
+API without a case here fails the build rather than a user's password reset.
+
 ## 11.0.0
 
 ### Read before upgrading

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@koolbase/js",
-  "version": "11.0.0",
+  "version": "11.2.0",
   "description": "Koolbase SDK for the browser \u2014 auth, database, storage, realtime, functions, flags and offline sync in one package.",
   "main": "./dist/cjs/index.js",
   "types": "./dist/esm/index.d.ts",
@@ -25,7 +25,7 @@
     "url": "https://github.com/koolbase/koolbase-react-native"
   },
   "dependencies": {
-    "@koolbase/core": "11.0.0"
+    "@koolbase/core": "11.2.0"
   },
   "publishConfig": {
     "access": "public"