Features, fixes, and version history. Each release is also published on GitHub Releases and crates.io.
--description or a comment --body now becomes a real Jira table instead of raw pipe characters. Thanks to @fabianderschatta.confluence page comments failed on any page that had at least one comment. It now also shows the comment body, with a new --full flag for untruncated text. Thanks to @alexevansigg.confluence attachment download dropped the /wiki path segment and always failed with a 404.aes-gcm to 0.11 and indicatif to 0.18.6, and updated quinn-proto, crossbeam-epoch and anyhow to clear security advisories.jira issue create and jira issue update take a --sprint <id> flag that assigns the issue to a sprint via the Agile API, so you no longer need to look up the board's customfield_10020 id by hand.issue get — jira issue get now displays the issue's sprint, so you can verify sprint assignment without a raw REST call.zeroize to 1.9.0.issue get — the output now includes an attachments array (id, filename, MIME type, size, download URL) in JSON, table, and markdown. Tolerant of Jira returning the attachment id as either a number or a string.jira issue comments list --full — returns the complete comment body instead of the 50-character preview.issue create/update --description and comment bodies convert Markdown (headings, lists, bold, italic, inline code, links, code blocks) into structured Atlassian Document Format. Plain text still becomes a single paragraph.confluence folder get | create | delete command group for /wiki/api/v2/folders.pipeline trigger --custom-pipeline <name> runs a named custom pipeline.issue update, transition, assign, and Confluence equivalents) no longer report false errors on an HTTP 204 No Content response. Exit codes are now reliable.proc-macro-error2 dependency and refreshed the dependency set.--field, ADF markdown extraction in issue get, and a range of Bitbucket and Confluence improvements across the 0.3 line.Full notes for every prior version (0.3.2 back to 0.1.0) are on GitHub: