Releases: bytepunx/authstar-clients
Releases · bytepunx/authstar-clients
Release list
core: v2.1.0
fastify: v2.0.1
fastify: v2.0.0
2.0.0 (2026-08-29)
⚠ BREAKING CHANGES
- fastify: fastify fully bundles core's source at build time (tsup --noExternal), so request.authstar's decorated shape changes to match core 2.0.0 -- organizationMemberships replaces organizationId, same breaking change, just carried through the bundle rather than fastify's own source changing.
Features
- fastify: rebuild and republish against core 2.0.0 (3e4f742)
core: v2.0.0
2.0.0 (2026-08-29)
⚠ BREAKING CHANGES
- core: InternalClaims.organizationId (an optional single id) is replaced by organizationMemberships: Array<{ organizationId, roles }>. An account can belong to more than one organization, each conferring its own independent role list (ADR 0100) -- callers must look up the relevant entry in the array instead of comparing against a single flat id. Always present (empty array), matching roles/ permissions' existing convention.
Features
- core: InternalClaims.organizationMemberships replaces organizationId (b8028fa)
fastify: v1.0.0
1.0.0 (2026-08-20)
⚠ BREAKING CHANGES
- fastify: perTenantJwksKeyProvider (re-exported from authstar-core) now takes a domain resolver function, not a baseDomain string -- same breaking change as core 0.3.0, just actually propagated this time.
Bug Fixes
core: v1.0.0
1.0.0 (2026-08-20)
⚠ BREAKING CHANGES
- core: perTenantJwksKeyProvider's first parameter changes from a baseDomain string to a (tenantSlug) => string | undefined | Promise<string | undefined> resolver function. Callers (tower, and web once it adopts this) must supply a resolver instead of a baseDomain -- see ADR 0091 for the recommended tower-backed, cached implementation.
Features
- core: perTenantJwksKeyProvider takes a domain resolver, not a baseDomain string (382c563)
