prreviewbuddy 0.36.4 → 0.39.3

package/CHANGELOG.md

@@ -1,5 +1,137 @@
 # Changelog
 
+## 0.39.3
+
+**Reviews of a branch now notice when the branch moves, not only reviews of a pull request.** The
+workspace server already checked the pull requests behind your queued, saved and in-progress reviews
+every few minutes. It now checks reviews with no pull request too, by looking at the branch they
+follow in your own repository, with no network access. When you commit to that branch, the review's
+card says **Branch updated** and you get a notification, the same way a moved pull request says
+**PR updated**. The card and the review page's **Check for updates** use the same check, so they
+always agree.
+
+**Fetch updates on the Reviews page.** A review that follows a remote branch, such as
+`origin/feature`, only moves when your repository fetches. **Fetch updates** fetches each repository
+once and then checks those reviews straight away, so a teammate's push shows up without opening each
+review. It covers the reviews the page is showing after search and filters. In selection mode,
+**Fetch selected** in the bar at the bottom covers only the reviews you ticked. Nothing is fetched
+unless you press one of them, reviews of a local branch are never fetched for (a fetch cannot move
+them), and your branches, checkout and working tree are never changed. If one repository cannot be
+reached the others still fetch, and the button says so: **Fetched 2 of 3 repositories**. Branches
+your fetch configuration excludes are left out rather than reported as fetched.
+
+**A tidier Reviews toolbar.** The five status buttons are now one **Status** menu, with the same
+choices and the queue count as **Queue (4)**, so search, filters and Fetch updates fit on one row.
+
+## 0.38.8
+
+**Update review replaces the review instead of running on top of it.** While an update runs, the
+middle of the page shows its progress in place of the findings that are about to be replaced. The
+sidebar is dimmed, and Buddy AI keeps its conversation but waits until the new review is ready. The
+page no longer flashes while an update runs: on reviews without a connected pull request it was
+reloading itself every second. When the update finishes the page switches to the new review once. If
+it fails, the previous review comes back unchanged with the reason.
+
+**Nothing you do during an update is lost any more.** Questions ticked, findings dismissed and Buddy
+AI answers given while an update was running could be overwritten when it finished. They are now kept,
+including when the update runs from the terminal and you are working in the browser at the same time.
+
+**The review header separates status from action.** "Review up to date" is now plain status, with a
+**Check for updates** button beside it. A check that finds new commits brings back a Code changed
+banner you had dismissed.
+
+**The "does not read pull request conversation" note can be dismissed.** Dismissing it hides it for
+that host. The reason stays on the PR context page.
+
+**Update results are easier to scan:** **Review updated · 7bc233f · 2 issues fixed · 1 new issue ·
+2 questions answered**.
+
+## 0.38.2
+
+Two gaps in the per-investigation summary added above: a finding revised a second time was left out
+of the count, so a run that regraded something could report "no findings changed"; and findings an
+earlier investigation had added were counted again by every investigation that followed.
+
+## 0.38.1
+
+A second repository investigation could undo the first one's conclusions. Findings an earlier
+investigation had confirmed or refuted went back to plain "Investigated" whenever the new evidence
+had nothing to say about them, while the sentence explaining the original conclusion stayed on the
+card beneath it. A conclusion now survives an investigation that does not bear on it, and only
+evidence that positively changes it can replace it. Each investigation's summary counts what that
+investigation moved, rather than everything concluded so far.
+
+## 0.38.0
+
+**PR Review Buddy notices when a reviewed pull request moves.** The workspace server checks the
+pull requests behind your queued, saved and in-progress reviews every few minutes, using the `gh`
+you are already signed in to, and records one notification when a request gains commits: **PR
+updated - 3 new commits**, linking to the review, where **Update review** is still yours to press.
+Nothing is re-analysed for you, nothing is reordered, and nothing about the review changes. Reviews
+of a local branch or a single commit are not watched, because there is no pull request to watch.
+
+Also fixed, and older than the above: **updating a review could reopen findings and questions an
+earlier update had already settled.** Each update judged the whole list against only the newest
+commits and was never told what the previous update had concluded, so a fix or an answer from two
+commits ago read as "these changes do not address it". Verdicts now travel forward, a resolved
+finding stays resolved, and an answered question keeps its answer - including on reviews already
+left in that state, whose answers are recovered on their next update.
+
+
+## 0.36.10
+
+**Syntax highlighting in the file viewer.** Code opened in the review is now coloured by language:
+Ruby, JavaScript, TypeScript, JSX, TSX, JSON, YAML, Markdown, HTML, CSS, SCSS, SQL, Python, Java,
+Kotlin, Go, Rust, shell scripts, Dockerfiles and Terraform. Added, deleted and cited lines keep
+their shading, with the colours inside it. Other files show as plain text, as before.
+
+Colouring loads in the background once the review opens, and only for the languages that review
+changed, so a file usually opens already coloured. When it isn't ready yet, the text shows straight
+away and the colour follows. A very long line is coloured as far as it is shown, and in full once you
+press Show full line.
+
+## 0.36.9
+
+A file opened from the review guide, an issue, a question or a KISS finding now joins onto the link
+that opened it, the way a row in the Files tab already did. The file name and its code read as one
+card, and the file name stays exactly where it was when the code opens.
+
+## 0.36.8
+
+**Expand the file viewer.** A new Expand button beside Open in VS Code makes a file's code as tall
+as the review column allows, with the review path and Ask panel left where they are. Collapse
+returns it to its usual size, and the line you were reading stays in view both ways. The button
+only appears when the file is longer than the viewer.
+
+An open file row and its code now read as one card, joined with no gap between them.
+
+The first press of **Show more of this file** on a file opened from its row now shows more. It
+used to ask for the 600 lines already on screen and change nothing.
+
+## 0.36.7
+
+**Step between the changes in a file.** The file viewer now has Previous and Next beside the
+version caption, with a count such as `2 of 6`. A replaced line and its removal count as one
+change. Next goes to the first change below where you are, including the line a finding opened
+you on, and brings a change outside the lines on screen into view. A removed block is shown by its
+marker and stays collapsed.
+
+## 0.36.6
+
+A very long line in the file viewer, such as minified code or generated data, is now cut short
+after 1,000 characters with a **Show full line** control beside it. Opening a file no longer lays
+out tens of thousands of characters at once. The whole line is still there, one click away.
+
+## 0.36.5
+
+**The file viewer shows where lines were removed.** A file could say `+9 −1` while the viewer only
+ever shaded the nine, because it shows the file as reviewed and a removed line is not in it. Now a
+small `− 1 deleted line` marker sits exactly where the removal happened, and clicking it shows the
+old lines in place, above whatever replaced them. It is still the whole file rather than a diff.
+
+If the recorded change for a file cannot be read reliably, the viewer says `change details
+unavailable` and marks nothing, rather than shading lines in the wrong place.
+
 ## 0.36.4
 
 The search box and filters on the reviews list now sit over the list itself, sharing its column,