Gate for TypeScript changelog
Release notes for @k9o/gate, from the CHANGELOG.md in the sdk-gate-typescript repository. Read on 17 November 2026 at 15:55 UTC.
1.5.2
Changed
- The
tierGatingoption is removed from sign-in provider creation; the platform no longer gates features by plan. - README: Architecture at a glance, illustrations, and the package table lists only the packages for that SDK.
1.5.0
Changed
- Breaking: provider sign-in no longer puts tokens in the redirect URL.
signInWithProviderkeeps a one-time verifier (sessionStorage, orstorage) and sends its S256 challenge; the browser returns toredirectUri#code=..., and the newcompleteSignIn(hash?, { storage? })exchanges the code and the verifier for the session (POST /gate/idp/exchange).parseSignInCallbackis removed. Apps on 1.4 and earlier must upgrade for provider sign-in to work. - A gateway error code the SDK does not name is kept as
GateError.codewith its full wire code (for exampleK9O_MAGIC_LINK_REDIRECT_NOT_CONFIGURED), no longer collapsed toINTERNAL_ERROR.GateErrorCodenow also admits any string.context.originalCodeis unchanged.
Added
-
mfa.methods.list()(GET /gate/mfa/methods) andmfa.methods.delete(methodId, { code? })(DELETE /gate/mfa/methods/{methodId}): an end user lists and removes their own second factors, with their access token (partnerTokenor{ bearerToken }). Removing a confirmed authenticator needs its current code. New types:MfaMethod,ListMfaMethodsResult,DeleteMfaMethodInput,DeleteMfaMethodResult. -
Methods for the end-user flows the gateway already serves, as the wire layer only (none calls a passkey API):
passkeys.register.beginand.finish,passkeys.signIn.beginand.finish,mfa.totp.enrolland.confirm,passwordReset.requestand.redeem,invitations.redeem, andverifySession. The calls that need an end user's access token (passkeys.register.*,mfa.totp.*, andverifySession's own authentication) usepartnerTokenor a per-call{ bearerToken }; the others send none. New types:BearerOptions,MfaChallenge,PasskeyRegistrationOptions,PasskeyAuthenticationOptions,PasskeyRegistrationResponse,PasskeyAuthenticationResponse,FinishPasskeyRegistrationInputandResult,BeginPasskeySignInInput,FinishPasskeySignInInputandResult,EnrollTotpInputandResult,ConfirmTotpInputandResult,RequestPasswordResetInputandResult,RedeemPasswordResetInputandResult,RedeemInvitationInputandResult,VerifySessionInputandResult. -
One-time codes, magic links and password-reset requests are limited for each email address, and a code is spent after 5 wrong guesses.
verifyOtpthrowsINVALID_CREDENTIALSfor a wrong code andRATE_LIMITED(withretryAfterSec) over a limit. This needs gateway2.71.75-betaor later; on an older gateway codes can be guessed without limit. -
signInWithProvideracceptsapple,facebookandtwitteras well asgoogle,github,microsoft,oidcandsaml. -
magicLinkRedirects.setDefault(id): make a registered redirect the default (PATCH /gate/magic-link-redirects/:idwith{ isDefault: true }); the previous default is demoted in the same step. -
GateError.publicMessage: a fixed sentence chosen by status class, for showing to end users. Never built from gateway text. -
GateError.requestId: the gateway'sx-k9o-request-idresponse header, ornull. -
errorsoption oncreateGateClientandconfigureGate:"full"(default) or"redacted". Redacted keeps the code, status,requestId,publicMessageandretryAfterSec, and dropsmessage,recommendationandcontext. An invalid value throwsK9OGateConfigErrorwithK9O_INVALID_FIELD_VALUE. -
Password sign-in, one-time-code request and verify, and magic-link send first ask the project which region holds the email. If the project's locate step answers 404, the client uses the base address; any other failure of that step is raised as before.
-
orgSlugoption oncreateGateClientandconfigureGate, as an alternative tobaseUrl. Alone it meanshttps://<orgSlug>.api.k9o.io; with a platform host such ashttps://api.k9o.ioit gives that host's organization form. A full organizationbaseUrlor a custom domain is used as given. With neither, or with a malformed slug, construction throws the newK9OGateConfigError(aGateError) with codeK9O_INVALID_BASE_URLorK9O_INVALID_FIELD_VALUE.baseUrlis now optional in the type. -
SignInStoragetype, andverifier_missingas aSignInCallbackResulterror.
Fixed
- A gateway error whose
recommendationis an object ({ action }or{ retryAfterSec, note }) now gives the action text (or note) asGateError.recommendation, and any other non-string givesnull.GateError.retryAfterSecholds the wait the gateway asked for, ornull. CreateIdpInput.redirectUriis optional, as it is at the gateway (which derives the callback URL). A call that omitted it failedtsc.verifyJwtacceptsEdDSAby default. Gate signs project tokens with EdDSA, so a token verified withoutallowedAlgorithmswas rejected asALGORITHM_NOT_ALLOWED.
1.4.0 — 2026-10-26
Added
- README sections on identity federation and data scoping.
Changed
- README description.
1.3.0 — 2026-10-26
The SDK now matches the gateway routes exactly.
Changed
signOutrequires{ refreshToken }and returns{ revoked }.whoamireturns the end user record itself.refreshTokenreturns{ accessToken, expiresAt }. The refresh token is not rotated.passwordless.requestOtpreturns{ otp: { id, expiresAt }, debugCode? }.passwordless.verifyOtpreturns{ verified, session?, endUserId? }.sessionis set only for thesigninpurpose.passwordless.requestMagicLinkreturns{ magicLink: { sent, expiresAt? }, debugLink? }.passwordless.verifyMagicLinkreturns{ redeemed, session, endUserId }.verifyJwt({ jwksUrl })reads the gateway's envelope-wrapped key set. The route isGET /@{projectSlug}/auth/jwks.- Regional host lookup works for any
<org>.api.<apex>host. No apex is hardcoded.
Removed
verifySessionandhosted: the gateway has no route for them.
Added
fetchoption onverifyJwtand the exportedfetchJwkshelper.
1.2.0 — 2026-10-25
- The README now introduces the Kilimanjaro building blocks (Keep, Pulse, Gate, Kibo). No change to the public API.
1.1.1 — 2026-10-25
- Documentation links corrected: the documentation hub is https://docs.kilimanjaro.dev, with the website, platform API and console listed in a Links section. Package metadata points at the same places.
1.1.0 — 2026-10-25
- Documentation rewritten with runnable examples and expected output; internal cross-references removed from the published sources. No change to the public API.
1.0.0 — 2026-10-23
First public release. See the README for the full API overview.