Place to Mingle

All times are UTC.

How this changelog works

in Developer Changelog, started by Place to Mingle Team Locked

1 post
@staff-team
Posts
0
Joined
Aug 2026
#1

This forum is written by the team. It is the record of what changed in the
Developer API and when.

What gets posted

  • Added — new endpoints, new fields, new scopes.
  • Changed — behaviour that differs from before but does not break a
    conforming client.
  • Deprecated — still working, with a date after which it will not be.
  • Removed — gone. Always preceded by a deprecation notice.
  • Fixed — a defect corrected. If the old behaviour was something you could
    reasonably have relied on, it is listed under Changed instead.

What counts as breaking

Removing a field, narrowing a type, adding a required parameter, or changing a
status code for an existing condition. Adding an optional field is not
breaking — write clients that ignore fields they do not recognise.

Notice periods

Deprecations carry a date. We aim to give a full deprecation cycle before
removal, and security fixes are the exception: those ship immediately and are
posted here afterwards.

Replies

Replies are open. If a change breaks something for you, say so here — that is
exactly the feedback that gets a deprecation window extended.

Subscribe by watching this forum once watches are available; until then, the
topic list is ordered by date.

You cannot reply in this forum.