@troylar/flightdeck 2.4.0 → 2.6.0

package/CHANGELOG.md

@@ -2,6 +2,29 @@
 
 <!-- Generated by build.py from src/releases.json. Edit that file, not this one. -->
 
+## 2.6.0 · Oct 25, 2026
+
+Boxes that explain themselves.
+
+### Improved
+
+- **Every box asks a question, with an example and why it matters** (Editor). Each box in the step form asks what to put there ("Which job?", "What do you run?"), shows an example in gray and says what it's used for and what happens when it's left empty. Phases, gates, lanes, checklist details, screenshots and Questions ask too. *Where:* Editing a checklist, the step form and the other forms
+- **Only the boxes a step usually needs are shown; the rest are one click away** (Editor). A step shows the boxes its type usually needs and any that hold a value. The others wait behind "+ add" buttons, and the fields every step accepts (a link, how long it takes, a deadline, proof, a time) are under More about this step. A value the step doesn't use, such as another action's field, is kept and says why. *Where:* The step form
+- **Short choices are buttons, and the step says what checking it will ask for** (Editor). A choice of five or fewer (an action, Ask for proof, how a phase is worked) is a row of buttons you can also move through with the arrow keys. What must be recorded offers only names the step can record, and When it's checked, they record lists exactly what the run will ask for. *Where:* The step form and the phase form
+- **One Pull request step, with GitHub or Bitbucket as its first question** (Editor). The parts box and the type picker have one Pull request. Its first question is Where is the pull request?, GitHub or Bitbucket; switching keeps every value and points out what the other one doesn't use. A new one uses the host the checklist already uses most. *Where:* The parts box, the type picker and the step form
+- **Fill in and the record form ask the same questions** (Runs). Filling in a step or recording what you did asks the box's question, shows an example and says why under the box. The step's What to do now names every kind of proof: a link, a note, a number, a yes or no, or a date. *Where:* The run screen and practice
+
+## 2.5.0 · Oct 25, 2026
+
+Big folders.
+
+### Improved
+
+- **A team folder with thousands of runs opens and refreshes without stalling** (Everywhere). Refreshing a folder of thousands of runs no longer freezes the page, even when many runs can't be read for a while (as OneDrive placeholders can't) and then come back. *Where:* Opening and refreshing the team folder
+- **The first open stays responsive while runs arrive** (Everywhere). While runs are still arriving, the page updates at most every quarter second, with the count read so far. Anything you click answers at once, and the page is complete as soon as the last run is read. What you're typing keeps its place. *Where:* Opening the team folder
+- **Screens with hundreds of processes and people draw quickly** (Everywhere). Home, the runs list, process pages, every person picker and Settings, People open quickly with hundreds of processes and people. *Where:* Home, Runs, process pages, person pickers, Settings
+- **Folder health finds leftover save receipts quickly** (Folder health). Folder health finds leftover save receipts quickly, even in a large team folder. *Where:* Settings, Folder health
+
 ## 2.4.0 · Oct 25, 2026
 
 Fresh coat.