Reported by: sister team during the v0.2.4 RC soak (see #286).
Severity: docs nit — deferred out of v0.2.4 (tag not moved), target 0.2.5. Roll into the 0.2.5 next-cycle PR.
The ## [0.2.4] df.list_instances() changelog entry does not match the shipped columns:
- It says
created_at/updated_at timestamps — there is no updated_at; the paginated overload returns completed_at (and next_cursor).
- It should also make clear the new columns/filters (
label_filter, after_cursor/next_cursor, timestamps) are on the paginated overload, not the basic 2-arg form.
Note: the shipped v0.2.4 GitHub Release notes were already hand-corrected; only the committed CHANGELOG.md at the tag still has the old wording. Fix CHANGELOG.md in the 0.2.5 cycle.
Reported by: sister team during the v0.2.4 RC soak (see #286).
Severity: docs nit — deferred out of v0.2.4 (tag not moved), target 0.2.5. Roll into the 0.2.5 next-cycle PR.
The
## [0.2.4]df.list_instances()changelog entry does not match the shipped columns:created_at/updated_attimestamps — there is noupdated_at; the paginated overload returnscompleted_at(andnext_cursor).label_filter,after_cursor/next_cursor, timestamps) are on the paginated overload, not the basic 2-arg form.Note: the shipped v0.2.4 GitHub Release notes were already hand-corrected; only the committed
CHANGELOG.mdat the tag still has the old wording. FixCHANGELOG.mdin the 0.2.5 cycle.