Skip to content

v0.1.1

Choose a tag to compare

@github-actions github-actions released this 09 Oct 04:11
· 163 commits to main since this release
13c0b65

From two integration reviews: a public origin and a standard OIDC issuer for the published
images, second-factor policy and company administrators through the gateway, service accounts
as members, org reads and SDK parity, and package publishing.

  • Go 1.26.9 toolchain and builder image (ten standard-library advisories in net/http, net/textproto and crypto/tls, GO-2026-6603 to GO-2026-6617); the release gate's govulncheck blocked the tag on 1.26.8

  • golang.org/x/text 0.41.0 (GO-2026-6629, a panic on crafted input in the precis package that pgx reaches on connect); the release gate's govulncheck blocked the 0.1.1 tag on 0.40.0

  • Compose marks Keycloak healthy only on a 200 readiness status, not on any "status": "UP" fragment; bootstrap's readiness wait grows from 30s to 90s, so a cold first docker compose up --wait no longer fails

  • Authz debug check answers an engine refusal as 422 VALIDATION_FAILED (was the VALIDATION_ERROR shape code)

  • Quickstart "What to try first" points at the admin routes instead of a removed section

  • The discovery document's issuer equals the iss every token carries (<origin>/realms/<realm>) at both /auth/realms/… and /realms/…, so a standard OpenID Connect library accepts Kiban's tokens; the /realms/ mount forwards Keycloak untouched, so a login started there completes

  • An object carries one company anchor: the grants route refuses a second anchor with 422 and migration authz/0012 adds the unique index behind it; a repeated tuple is still a no-op; the grant ledger records changes only (a duplicate grant or a revoke of a missing tuple no longer writes a phantom row)

  • Kubernetes: apply.sh waits only for the Deployments the overlay created, so a core-only apply no longer fails on the absent sample modules; the gateway receives KIBAN_DOMAIN and KIBAN_EXTRA_ORIGINS from kiban-config, as bootstrap already did

  • The Kustomize base carries no Secret, so it works as a remote base from another repository; each overlay supplies kiban-secrets (gen-secrets.sh <overlay> writes it there and moves a 0.1.0 base/secret.yaml into place); make k8s-check renders base and overlays without a cluster

  • Zero-clone quickstart serves a real origin: deploy/quickstart/compose.public.yaml (generated from the source overlay) sets the public issuer, Keycloak hostname, KIBAN_DOMAIN and KIBAN_TRUSTED_PROXY from one KIBAN_PUBLIC_HOST

  • Second-factor policy through the gateway: GET/PUT /api/platform/admin/mfa-policy/global, GET/PUT/DELETE .../users/{subject}, POST .../sync (superadmin); documented on the Operating page, with the note that a new realm requires no second factor

  • Members carry kind (person or service): identity records whether a user is a client's service account (confirmed through Keycloak's client link at provisioning), and the member directory and admin member routes return it; bootstrap grants identity's service account the read-only view-clients role for that check and repairs it on an existing realm

  • Docs: an app's service account is a user; to run background jobs in a company it must be made a member of that company (the two admin calls), while writing tuples on the app's own types needs no membership

  • A company's administrator (company:<id>#admin) manages that company's members, positions, assignments and groups through /api/org/admin/*; the gateway and org both decide "superadmin, or administrator of this company"; companies and org units stay superadmin work

  • Two company reads for apps and members: a position's holder on a date (GET /api/org/companies/{id}/positions/{positionId}/holder?date=) and a group's members, for any active member of the company or a superadmin, never across companies

  • SDK parity: batch checks, companies the user may see, member directory, position holder and group members in the Go, Node (server) and Python SDKs; Python gains batch_can

  • Each sample module has its own Compose profile beside samples: COMPOSE_PROFILES=docs starts one container, not four

  • Releases publish kiban-sdk to PyPI and @rossbsol/kiban-sdk to the public npm registry when the repository holds PYPI_APIKEY and NPM_TOKEN; both packages are also attached to the workflow run as artifacts. The npm package is renamed from @rosschiu/kiban-sdk (never published publicly) and GitHub Packages is no longer used

  • Full changelog: https://github.com/rosschiu/kiban/blob/v0.1.1/CHANGELOG.md

  • Known limitations: https://rosschiu.github.io/kiban/limitations/