Renaming a label moves its records and Minis
v1.14.0 Change a label’s name with PUT /api/v1/Labels/{id} and every record and Mini carrying it moves to the
new name, so nothing is left holding a name the label no longer answers to. The move runs in the background, so the
response carries a new rename field naming the previousName still being swept; it disappears once the move is done,
and GET /api/v1/Labels reports the same field while you wait. Its presence is the whole signal, so poll until it goes.
A label’s resourceType can no longer be changed and returns 400; create a label of the intended type instead.
Editing or deleting a label whose rename has not finished returns 409. A sweep that hits a transient failure retries
itself.
The processing record state is gone
v1.12.0 RecordState no longer has processing; a record is now active, draft, archived, or deleted, and
new records come back active straight away. If you branch on or filter by state, drop the processing case (it is
removed from RecordDto.state, the GET /Records states filter, and GET /Records/filters/states). Records created
under the old state come back as active, so nothing is left unreadable.