Releases
Every release of the registry, newest first, and what changed in the shape of the data.
The registry is released a few times a year. Each release is an immutable folder on the API and a tagged release on GitHub; the notes on GitHub say why, and changes.json at the root says exactly what changed in the data. The schema version is what a client cares about: while it stays the same, the shape of every record is the same.
| Release | Date | Schema | What changed | |
|---|---|---|---|---|
v3.4.0 this site | 2026-09-22 | 12 | 1 printing changed · 1 note added | Notes |
v3.3.3 | 2026-09-17 | 11 | no data changes | Notes |
v3.3.2 | 2026-09-17 | 11 | no data changes | Notes |
v3.3.1 | 2026-09-15 | 11 | not recorded | Notes |
v3.3.0 | 2026-09-15 | 11 | not recorded | Notes |
v3.2.1 | 2026-09-15 | 10 | not recorded | Notes |
v3.2.0 | 2026-09-14 | 10 | not recorded | Notes |
v3.1.0 | 2026-09-14 | 9 | not recorded | Notes |
What each release changed
From v3.3.2 on, every release root carries changes.json: the way from the previous release, as counts and the ids behind them. Each record names the fields that differ. Identifiers removed is always 0 within a major; the release workflow refuses to publish otherwise.
v3.3.3 → v3.4.0
1 printing changed · 1 note added · 0 identifiers removed · schema 11 → 12
1 printing changed
P001640: released_with
1 note added or removed
P001640: Prize support in the Arthurian Legends store kit, sent to stores for Organised Play when the set released. Each kit held three of this Sorcerer. Stores could reportedly request a second kit, which shipped with a Cornerstone kit. Source: Community report, Sorcery Discord. The release date on record, 2024-10-04, is Arthurian Legends' own.
v3.3.2 → v3.3.3
0 identifiers removed
v3.3.1 → v3.3.2
0 identifiers removed
Schema changes
A change that only adds fields raises the schema version and ships as a new v3 release. A change that would break an existing reader becomes a new major with its own alias. The migration guide maps every field that changed at each schema version, from v1.x onward.
Follow releases
- Poll
versions.json: once an hour is plenty. See releases and versioning. - Watch the GitHub releases, which carry the notes and can notify you.
Reference: registry API contract and published object definitions. Report a data or documentation issue.