Changelog

Changes to the Akin partner API, SDK, and GraphQL schema. Each release is its own entry in the sidebar, newest first.

Subscribe

Point your feed reader at /changelog.rss to get every release as it ships — no email signup required. The feed is regenerated from the entries below on every docs build.

When we publish an entry

Any change to the partner-facing surface gets a changelog entry:

• GraphQL resolvers (apps/api/src/resolvers/)
• Domain entities and their exposed fields (packages/domain/)
• The partner SDK (packages/partner-sdk/)

The changelog-snippet CI gate fails a PR that touches those paths without adding an entry. Internal-only changes that happen to live under those paths can opt out with the skip-changelog label.

Adding an entry

Create one MDX file per release at content/changelog/<YYYY-MM-DD>.mdx and add it to _meta.ts above the previous release. Use this template:

---
title: Short release summary
date: 2026-06-03
version: 2026.06.03
---
 
# 2026-06-03 — Short release summary
 
## Added
- New thing ([#1234](https://github.com/akin-travel/issues/issues/1234)).
 
## Changed
- Behaviour change, with migration notes ([#1235](https://github.com/akin-travel/issues/issues/1235)).
 
## Deprecated
- Field marked `@deprecated`; removal date and replacement ([#1236](https://github.com/akin-travel/issues/issues/1236)).
 
## Fixed
- Bug fix ([#1237](https://github.com/akin-travel/issues/issues/1237)).
 
## Security
- Security-relevant change ([#1238](https://github.com/akin-travel/issues/issues/1238)).

Rules

• date is YYYY-MM-DD; version is the release version (we use YYYY.MM.DD).
• Omit any section (Added / Changed / Deprecated / Fixed / Security) that has no items — don’t ship empty headings.
• Every item links to the PR or issue that introduced it.
• The frontmatter is required: the RSS generator parses title, date, and version from it, and fails the build if any is missing.