prreviewbuddy 0.73.1 → 0.75.0

package/CHANGELOG.md

@@ -1,5 +1,100 @@
 # Changelog
 
+## 0.75.0
+
+**You can change a finding's grade.** An issue's severity and a question's importance are no longer
+fixed by the analysis. Click the grade on a card, pick another, and optionally say why. The card
+shows the grade you hold now and how it moved, for example `major → minor · Reassessed by you`, with
+a History disclosure listing every change, its reason and when it was made. The analysis itself is
+never rewritten, so the original grade is always there to compare against.
+
+**Buddy AI can suggest a grade change, and you decide.** Reassess, in a card's Ask Buddy menu, asks
+Buddy AI to judge the finding again. If it thinks the grade should move, the card shows the
+suggestion with its reason and the places it cites, which open their file. Accept it, keep the grade
+you have, or ask more. A suggestion made against an older state of the review, or against a grade
+you have since changed, is shown as out of date rather than applied.
+
+**Updates and investigations suggest grade changes instead of making them.** When new commits change
+how serious a finding is, the update suggests the new grade and the update strip says how many it
+suggested. A repository investigation in the extension used to overwrite an issue's severity; it now
+suggests it, and can suggest a question's importance too. A collapsed list of closed findings says
+how many suggestions are waiting in it.
+
+**Your grades carry forward.** Prompts for chat, updates and investigations state the grade you hold,
+not the analysis's, so the next round starts from your judgement. Copy includes the change and its
+reason. An update never erases a grade change, and neither does a Look closer run or an
+investigation that finishes while you work.
+
+**The extension keeps what you do while a run finishes.** A grade change, dismissal or answer made on
+a review just as an update, investigation or Look closer saves its result is carried to the new
+result, and the sidebar catches up with it. Two Look closer runs finishing together both keep their
+findings. A reply that arrives late never puts an older grade back on screen. (Extension 0.26.0.)
+
+## 0.74.1
+
+**`review --pr` now works for pull requests from forks.** Before, a pull request whose branch lives on
+the contributor's fork could not be reviewed unless its commit was already in your clone, and the
+error told you to fetch a branch that does not exist on your remote. Now the pull request's own head
+is fetched from the repository it was opened against, so pasting the URL is enough: no fork remote,
+no `gh pr checkout`, no manual fetch. Nothing in your checkout changes, and no branch is created.
+
+**It works when your `origin` is your own fork.** The repository the pull request belongs to is found
+among your remotes, or reached by its URL when none of them is it. Only the exact commit GitHub names
+is ever reviewed; a fetch that brings anything else is refused rather than reviewed.
+
+**Updating a pull request review follows the pull request, not a branch of the same name.** A fork's
+pull request from its own `main` used to be updated against your repository's `main`. Update now
+asks GitHub where the pull request is and fetches its base too, so a pull request that merged the
+latest base is not shown the base's changes as its own.
+
+## 0.74.0
+
+**Notifications is now Activity, a history of what happened across your reviews.** Every row says
+more than what kind of event it was. A branch or pull request that moved says where it moved from and
+to, whether it moved locally or on the pull request, and how far behind the review was. A finished
+review says how many issues and unanswered questions it left. An update says what it fixed, what is
+new, what is still open and which questions the new commits answered. A failure says why. Each row
+records what was true when it happened, so an older row never changes its meaning.
+
+Each kind of event has its own icon: a branch, a commit, a merge, a check, a refresh, a warning.
+Unread rows keep their dot and tint, so new activity still stands out first. Purple now means only
+unread: pull request merges, closes and reopenings are shown in blue.
+
+**A branch that moves twice keeps both moves.** Before, a second move deleted the first row while it
+was still unread, and an update that caught the review up deleted it too. Now every move stays in
+Activity. Only the newest move counts as unread, since that is the only head you can update to, and
+an older one says "replaced by a later move" or "replaced when the review caught up". Neither is
+counted as read: nobody saw them.
+
+**PR merge, close and reopen transitions are now recorded in Activity, including changes discovered
+after a review is Done.** A pull request that merged or closed after you marked its review Done, or
+that was noticed by the hourly check or by Check for updates, used to change the card and say
+nothing. It is now in Activity, noting when the review had already been marked Done. A reopened pull
+request is now recorded too. One known gap: a pull request closed, reopened and closed again without
+a new push shows the second close only on its card, not as a second row.
+
+**Activity and Settings keep the bell current.** The Activity page adds new rows and quietens rows
+you read elsewhere while it is on screen, and asks again the moment you switch back to it. The bell
+on Settings now updates as well. Toasts stay to one line, with at most one detail.
+
+**Activity says how much history it keeps.** It keeps the most recent 200 events for up to thirty
+days. On a busy machine the 200 is reached first, so the page now says both rather than promising
+thirty days.
+
+## 0.73.2
+
+**Notifications about a review are marked read while that review is on screen.** Until now,
+opening a review marked its notifications read once, when the page loaded, so anything that arrived
+while you stayed on it, such as "Branch updated" after a commit, kept the bell lit long after you
+had seen it. Now a review page marks its own notifications read whenever it is visible: when it
+loads in front of you, when a tab you left in the background becomes visible again, and as new
+ones arrive while you are looking at it. The bell and the rail update at the same moment.
+
+A review page that is not visible marks nothing. Opening a review in a background tab, or leaving
+one open behind other tabs, keeps its notifications unread until you switch to it. Notifications
+about other reviews are never marked by a review page. This works on a review opened straight from
+a terminal link, too.
+
 ## 0.73.1
 
 **A review's first update says how long updates take.** While an update runs, the page now