Changelog
Release notes for the XKOVA API. Each entry records what changed in the public surface, so you can tell at a glance whether an upgrade needs work on your side. Breaking changes never land quietly here.
Current Versions
| Component | Version | Stage |
|---|---|---|
| API service | v0.1.1-alpha | Pre-launch alpha |
@xkova/sdk | 0.1.0-alpha.6 | Alpha |
@xkova/browser | 0.1.0-alpha.6 | Alpha |
The HTTP namespace is /v1. OpenAPI document metadata and workspace package metadata
do not identify a deployed API release. See Versioning.
During pre-launch, contracts may change in place. Keep the API reference and both SDK packages aligned with your environment. Review the SDK changelog and repository releases when upgrading. This table identifies versions in the current source. npm distribution tags determine which package version an installation command selects. The table does not prove which build a particular environment has deployed or that a package version has completed npm publication.
How to read an entry
Every release entry groups its changes under fixed headings so you can scan for the parts that affect you. Each entry should state the affected component and whether an integrator must take action.
| Heading | What it lists |
|---|---|
| Added | New endpoints and new webhook events, each with a short purpose. |
| Changed | Behavior changes. A breaking change here is rare and is called out as such. |
| Deprecated | Surfaces scheduled for removal, with their sunset date. See Deprecations. |
| Fixed | Corrected behavior in existing surfaces. |
| Security | Security relevant changes. |
| Migration notes | What you must do to adopt the release, or a clear statement that nothing is required. |
Related
See Versioning for the compatibility policy, and Deprecations for how a surface is retired with notice.