Changelog
Where to find release notes and per-package changelogs.
AuthKit is versioned and published with Changesets.
It is a monorepo of independently versioned packages: a change to
@adonis-agora/authkit-server does not bump @adonis-agora/authkit-client, and each
package carries its own semantic version and its own CHANGELOG.md. That is deliberate —
most apps depend on a subset of the packages, and a shared version number would force
upgrades that carry no changes for them.
GitHub releases
All tagged releases (with aggregated notes across the packages published in that run) are here:
Per-package changelogs
Every package keeps a CHANGELOG.md next to its source, generated from the changesets
merged into main. These are the authoritative notes for an upgrade — read the changelog
of the package you are bumping, not the aggregate release.
| Package | Current version | Changelog |
|---|---|---|
@adonis-agora/authkit-core | 0.7.0 | CHANGELOG.md |
@adonis-agora/authkit-server | 0.57.0 | CHANGELOG.md |
@adonis-agora/authkit-client | 0.17.0 | CHANGELOG.md |
@adonis-agora/authkit-sdk | 0.6.1 | CHANGELOG.md |
@adonis-agora/authkit-react | 0.18.0 | CHANGELOG.md |
@adonis-agora/authkit-testing | 0.4.0 | CHANGELOG.md |
@adonis-agora/authkit-vault-aws | 0.3.0 | CHANGELOG.md |
@adonis-agora/authkit-vault-azure | 0.3.0 | CHANGELOG.md |
@adonis-agora/authkit-vault-gcp | 0.3.0 | CHANGELOG.md |
The version column is a snapshot of the packages at the time this page was written. npm
is the live answer — npm view @adonis-agora/authkit-server version — and the linked
changelog always leads with the newest entry.
Reading a version bump
Every package is still in 0.x, which changes what a bump means:
- Minor (
0.56.0 → 0.57.0) — the range that carries breaking changes. In semver's0.xrules the minor is the major. Read the changelog before upgrading. - Patch (
0.6.0 → 0.6.1) — bug fixes and additive changes that do not move an existing contract.
Because the packages are versioned independently but peer-depend on each other, a minor
bump in authkit-server or authkit-core frequently widens or re-pins the peer range in
the packages built on top of it. When an install reports an unmet peer dependency, bump the
whole family to the versions listed in the same release rather than upgrading one package
in isolation.
How releases work
A PR that changes a published package includes a changeset (pnpm changeset), which
records which packages changed, at which bump level, and the prose that lands in their
changelogs.
On merge to main, the Release workflow opens a "Version Packages" PR. It applies the
pending changesets: versions are bumped in each package.json, the changeset files are
consumed, and each affected CHANGELOG.md gets its new section.
Merging that PR publishes the affected packages to npm — with provenance, so the build origin of each tarball is verifiable against the workflow run that produced it.