prreviewbuddy 0.36.10 → 0.39.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -1,5 +1,83 @@
1
1
  # Changelog
2
2
 
3
+ ## 0.39.3
4
+
5
+ **Reviews of a branch now notice when the branch moves, not only reviews of a pull request.** The
6
+ workspace server already checked the pull requests behind your queued, saved and in-progress reviews
7
+ every few minutes. It now checks reviews with no pull request too, by looking at the branch they
8
+ follow in your own repository, with no network access. When you commit to that branch, the review's
9
+ card says **Branch updated** and you get a notification, the same way a moved pull request says
10
+ **PR updated**. The card and the review page's **Check for updates** use the same check, so they
11
+ always agree.
12
+
13
+ **Fetch updates on the Reviews page.** A review that follows a remote branch, such as
14
+ `origin/feature`, only moves when your repository fetches. **Fetch updates** fetches each repository
15
+ once and then checks those reviews straight away, so a teammate's push shows up without opening each
16
+ review. It covers the reviews the page is showing after search and filters. In selection mode,
17
+ **Fetch selected** in the bar at the bottom covers only the reviews you ticked. Nothing is fetched
18
+ unless you press one of them, reviews of a local branch are never fetched for (a fetch cannot move
19
+ them), and your branches, checkout and working tree are never changed. If one repository cannot be
20
+ reached the others still fetch, and the button says so: **Fetched 2 of 3 repositories**. Branches
21
+ your fetch configuration excludes are left out rather than reported as fetched.
22
+
23
+ **A tidier Reviews toolbar.** The five status buttons are now one **Status** menu, with the same
24
+ choices and the queue count as **Queue (4)**, so search, filters and Fetch updates fit on one row.
25
+
26
+ ## 0.38.8
27
+
28
+ **Update review replaces the review instead of running on top of it.** While an update runs, the
29
+ middle of the page shows its progress in place of the findings that are about to be replaced. The
30
+ sidebar is dimmed, and Buddy AI keeps its conversation but waits until the new review is ready. The
31
+ page no longer flashes while an update runs: on reviews without a connected pull request it was
32
+ reloading itself every second. When the update finishes the page switches to the new review once. If
33
+ it fails, the previous review comes back unchanged with the reason.
34
+
35
+ **Nothing you do during an update is lost any more.** Questions ticked, findings dismissed and Buddy
36
+ AI answers given while an update was running could be overwritten when it finished. They are now kept,
37
+ including when the update runs from the terminal and you are working in the browser at the same time.
38
+
39
+ **The review header separates status from action.** "Review up to date" is now plain status, with a
40
+ **Check for updates** button beside it. A check that finds new commits brings back a Code changed
41
+ banner you had dismissed.
42
+
43
+ **The "does not read pull request conversation" note can be dismissed.** Dismissing it hides it for
44
+ that host. The reason stays on the PR context page.
45
+
46
+ **Update results are easier to scan:** **Review updated · 7bc233f · 2 issues fixed · 1 new issue ·
47
+ 2 questions answered**.
48
+
49
+ ## 0.38.2
50
+
51
+ Two gaps in the per-investigation summary added above: a finding revised a second time was left out
52
+ of the count, so a run that regraded something could report "no findings changed"; and findings an
53
+ earlier investigation had added were counted again by every investigation that followed.
54
+
55
+ ## 0.38.1
56
+
57
+ A second repository investigation could undo the first one's conclusions. Findings an earlier
58
+ investigation had confirmed or refuted went back to plain "Investigated" whenever the new evidence
59
+ had nothing to say about them, while the sentence explaining the original conclusion stayed on the
60
+ card beneath it. A conclusion now survives an investigation that does not bear on it, and only
61
+ evidence that positively changes it can replace it. Each investigation's summary counts what that
62
+ investigation moved, rather than everything concluded so far.
63
+
64
+ ## 0.38.0
65
+
66
+ **PR Review Buddy notices when a reviewed pull request moves.** The workspace server checks the
67
+ pull requests behind your queued, saved and in-progress reviews every few minutes, using the `gh`
68
+ you are already signed in to, and records one notification when a request gains commits: **PR
69
+ updated - 3 new commits**, linking to the review, where **Update review** is still yours to press.
70
+ Nothing is re-analysed for you, nothing is reordered, and nothing about the review changes. Reviews
71
+ of a local branch or a single commit are not watched, because there is no pull request to watch.
72
+
73
+ Also fixed, and older than the above: **updating a review could reopen findings and questions an
74
+ earlier update had already settled.** Each update judged the whole list against only the newest
75
+ commits and was never told what the previous update had concluded, so a fix or an answer from two
76
+ commits ago read as "these changes do not address it". Verdicts now travel forward, a resolved
77
+ finding stays resolved, and an answered question keeps its answer - including on reviews already
78
+ left in that state, whose answers are recovered on their next update.
79
+
80
+
3
81
  ## 0.36.10
4
82
 
5
83
  **Syntax highlighting in the file viewer.** Code opened in the review is now coloured by language: