Versioning & releases
The @akin-travel/partner-sdk is published to the public npm registry. This page is the contract for how it’s versioned and how you find out what changed.
Install
npm install @akin-travel/partner-sdkPin a version you’ve tested and upgrade deliberately:
npm install @akin-travel/partner-sdk@^1.0Every published version carries npm provenance , so you can verify the build came from this repository’s release pipeline.
Semantic versioning
The package follows semver :
| Bump | Means | Example |
|---|---|---|
Patch (1.0.0 → 1.0.1) | Bug fix, no API change | A hook stops throwing on an edge case |
Minor (1.0.0 → 1.1.0) | New, backwards-compatible API | A new headless component |
Major (1.0.0 → 2.0.0) | Breaking change | A renamed or removed export |
@akin-travel/partner-sdk is post-1.0, so standard semver applies: upgrade patch and minor freely, and read the changelog before a major.
Breaking changes to the underlying GraphQL API are governed separately by the deprecation policy: nothing is removed without a published sunset date at least 90 days out.
Changelog
Every release ships a changelog entry describing what changed, generated from the release at publish time — no manual edits. Browse it at Changelog, or subscribe to the RSS feed linked there.
Deprecations are also announced in the changelog and surfaced through the schema’s @deprecated directives — see the deprecation policy for the full surfacing contract.