From 4b312a552d65ded3c63d74289e227f3584827e63 Mon Sep 17 00:00:00 2001 From: AJ Isaacs Date: Fri, 23 Oct 2026 10:54:55 -0400 Subject: [PATCH] build(help): ship help v0.2.0 with the Machines page v0.2.0 adds the Machines page (nest machine, default machine, per-machine support grid, machine lead-ins) and the machines, nest-machine and support-grid topic IDs. desktop-help.md now points at the help repo's version rules so the next release is numbered the same way. Co-Authored-By: Claude Opus 5.5 --- docs/desktop-help.md | 6 ++++-- scripts/help.json | 4 ++-- 2 files changed, 6 insertions(+), 4 deletions(-) diff --git a/docs/desktop-help.md b/docs/desktop-help.md index f8b004eb..24c218ce 100644 --- a/docs/desktop-help.md +++ b/docs/desktop-help.md @@ -37,8 +37,10 @@ and expands it into the package's `Help\` folder; both `Publish-Windows.ps1` and `Deploy-OpenNest.ps1` call it, and `build-info.json` records the help version. Pass `-HelpDirectory ` to either script to package a local build instead. -To ship new help: tag the help repo `vX.Y.Z`, wait for its release, then update `tag` -and `sha256` here (the release attaches `opennest-help.zip.sha256`). +To ship new help: tag the help repo `vX.Y.Z` by the version rules in its README +(Releases > Version numbers: MINOR for new pages or topic IDs, PATCH for fixes and +recaptures; tag only once the behavior it describes is on `master`), wait for its release, +then update `tag` and `sha256` here (the release attaches `opennest-help.zip.sha256`). When a UI change alters a documented screen or workflow, update or recapture the affected opennest-help pages (its README covers capture and markup). diff --git a/scripts/help.json b/scripts/help.json index cefc07ea..3441ee29 100644 --- a/scripts/help.json +++ b/scripts/help.json @@ -1,5 +1,5 @@ { "repository": "ajisaacs/opennest-help", - "tag": "v0.1.0", - "sha256": "6401b6589f561ed18067364f55aaa341117770044f8c904cfa705429cfa7f082" + "tag": "v0.2.0", + "sha256": "54e187d964dd34e34ac49385db56d8aecebc11221ec1c68ba0b63ee1aab3e65f" }