v0.5.0

Breaking Changes

• bb pullrequest comment create/update --line N now anchors the comment to line N of the new (head) version of the file, matching how users actually compute line numbers — against the PR's head, not its base. Previously --line was sent as the API's inline.from, which anchors to the old (base) side, so comments landed offset by the net insertions/deletions above that point #77
• --to is removed. Its documented "range end" semantics never matched a real Bitbucket API field, so keeping it would have meant silently flipping its side for any script that relied on it — a hard "unknown flag" error is the safer failure mode #77

Migration

• Anchoring to a line in the file as it exists at the PR's head: use --line N as before — it now points at the right line
• Anchoring to a line in the file as it existed in the base branch (e.g. commenting on a deleted line): use --from N, the explicit old-side anchor
• Any script passing --to needs to drop it; there is no replacement flag, since old-side and new-side anchoring are both already covered by --from/--line

Fixes

• FileAnchor.String() (used by comment list's file column) now renders old-side and new-side anchors distinguishably: path:1040 for the new side, path:990(old) for the old side #77