@troylar/flightdeck 2.6.1 → 2.7.0

package/CHANGELOG.md

@@ -2,6 +2,21 @@
 
 <!-- Generated by build.py from src/releases.json. Edit that file, not this one. -->
 
+## 2.7.0 · Oct 26, 2026
+
+Boxes that know your details.
+
+### New
+
+- **Type ^ to put a run detail in a step, a gate or a field** (Editor). Typing ^ in a step's text, a gate's approval or a text field lists the checklist's run details, with where each comes from; Enter or a click puts it in. Insert a detail does the same, and Add ^name as a run detail adds one you haven't listed yet. The detail stays where you typed it in the step's text. *Where:* Editing a draft, the step and gate forms
+- **A misspelled detail is marked, with a one-click fix** (Editor). Each ^detail in a box is marked: fine, not a run detail, or maybe not set yet at that step. A misspelled one offers Use ^environment, and one the run may reach before it's set names the step that sets it, with Show that step. *Where:* Editing a draft, under each box
+- **See a box filled in, the way a run will show it** (Editor). In a run: under a box shows it with the values from this checklist's latest run, exactly as the run screen will. *Where:* Editing a draft, under each box that holds a ^detail
+- **Rename a run detail everywhere at once** (Editor). Rename in Checklist details changes the detail in its list, step text, gate approvals, fields, only when and sets, as one Undo step. It says how often each detail is used, and refuses when another checklist receives the detail by that name. *Where:* Editing a draft, Checklist details
+
+### Fixed
+
+- **A caret that isn't a run detail stays as written** (Runs). A field like grep ^ERROR shows ^ERROR in a run, and Checks name it as a tip, with the detail it likely meant. *Where:* The run screen and Checks
+
 ## 2.6.1 · Oct 25, 2026
 
 Documentation that matches the app.

package/README.md

@@ -111,6 +111,10 @@ You don't have to write Markdown. **New process** on the Processes page asks for
 
 **The step form** asks a question for each box, with a gray example and why it matters. It shows only the boxes the step's type usually needs, and any that hold a value; the rest are one click away behind **+ add** buttons. The fields every step accepts (a link, how long it takes, a deadline, proof, a time) are under **More about this step**. A choice of five or fewer is a row of buttons. **When it's checked, they record** lists exactly what a run will ask for. In the outline, drag a step or press Alt+Up / Alt+Down to move it, and **Undo** and **Redo** step through changes.
 
+**Details in any box.** Type `^` in a step's text, a gate's approval or a text field to pick a run detail, or use **Insert a detail**. A misspelled one is marked with a one-click fix ("Use ^environment"), and a detail that may not be set yet at that step says which step sets it. **In a run:** under the box shows it filled in, with the values from your latest run. A caret that isn't a detail, like `grep ^ERROR`, stays as written. To rename a detail everywhere at once, use **Rename** in Checklist details; it refuses if another checklist receives the detail by that name.
+
+<p align="center"><a href="https://github.com/troylar/flightdeck/blob/main/docs/images/autocomplete-light.png" title="Open in GitHub's image viewer"><picture><source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/troylar/flightdeck/main/docs/images/autocomplete-dark.png"><img src="https://raw.githubusercontent.com/troylar/flightdeck/main/docs/images/autocomplete-light.png" alt="A Jenkins step's parameters box: typing ^en offers ^environment, a text detail asked when a run starts, or adding ^en as a new run detail" width="49%"></picture></a> <a href="https://github.com/troylar/flightdeck/blob/main/docs/images/rename-light.png" title="Open in GitHub's image viewer"><picture><source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/troylar/flightdeck/main/docs/images/rename-dark.png"><img src="https://raw.githubusercontent.com/troylar/flightdeck/main/docs/images/rename-light.png" alt="Checklist details: each run detail with how many places use it and Rename; renaming ^tag to build_tag lists the steps that follow it" width="49%"></picture></a></p>
+
 **Save draft** saves your work. **Review & publish** goes back to the process page: there you can compare the draft with the last version, write what changed in one line, and choose **Publish vN**. Anything that blocks publishing disables the button; suggestions don't. A save goes through only if the draft is still what you opened; if a teammate changed it meanwhile, nothing is saved and you choose between their version and yours. A shared folder can't lock a file, so edit a draft with one person (or one AI assistant) at a time.
 
 <a href="https://github.com/troylar/flightdeck/blob/main/docs/images/edit-light.png" title="Open in GitHub's image viewer"><picture><source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/troylar/flightdeck/main/docs/images/edit-dark.png"><img src="https://raw.githubusercontent.com/troylar/flightdeck/main/docs/images/edit-light.png" alt="Editing a draft as Markdown, with Practice, Save draft and Review &amp; publish in the header: the open corrections with links to their lines, the Markdown on the left, and the Checks and Preview tabs on the right"></picture></a>