Repository navigation
v0.27.1
Patch: linked_file attachments now actually create
v0.27.0 shipped a regression in --attach-file: zotagent force-set the filename field on the linked-file attachment payload, which Zotero's schema rejects with HTTP 400 ('filename' is valid only for imported and embedded-image attachments). Every --attach-file use produced an orphan parent item plus a warning instead of a proper attachment.
This release reverts to the template-gated set: filename is not sent for linked_file, and Zotero derives the attachment's display label from the basename of path. The mock template in tests already mirrored Zotero's real schema, so the regression slipped past the unit tests; an end-to-end smoke test against a live library caught it. Tests updated to assert filename is absent from the request body.
v0.27.0 users who pulled and tried --attach-file should upgrade. Orphan parent items left behind by the broken release are easy to find — they have a warning of the form Created parent item but attachment failed: ...filename is valid only for imported... in the add response — and can be cleaned up by deleting them in Zotero (or via the Web API) and re-running with 0.27.1.
Full Changelog: v0.27.0...v0.27.1