Changelog
What shipped, when — newest first. There is nothing here yet, and that is the accurate answer rather than a placeholder one.
Nothing has shipped
Cosend is in build. The specification is complete and this site describes what it specifies, but no release has gone out, so there is no release to list. The first entry here will be the first one there is.
We could fill this page. A changelog is one of the easiest things on a website to invent, and an invented one is one of the easiest to check — every entry names a feature, and a feature either exists or it does not. So it stays empty until it is not.
What an entry will mean
Worth reading once before you build against the API, because two of these are commitments rather than descriptions.
- Adding is not breaking
- A new field on a response, a new optional parameter, a new value in an enum: none of those is a breaking change and none of them will be announced as one. Your client has to tolerate fields it does not recognise — that is the contract, and it is the reason we can ship at all.
- Breaking means a new version
- Removing a field, changing a type, changing what an existing value means. That is /v2, announced twelve months ahead, with both versions live throughout. It will not arrive in this list as a line item one Tuesday.
- Meta’s changes are ours to absorb
- The Graph version you pin is yours and we forward it. When Meta deprecates one, that is an entry here with the date they published — not a surprise you find in a log.
- Incidents are not changelog entries
- Something breaking and being fixed is an incident, and incidents are posted where availability is reported. This list is what changed on purpose.
The versioning rules are in the REST API conventions, and availability is reported separately.