Skip to content

DEV-1357: say up front that a release needs a passing hardware test - #227

Merged
JongChern merged 1 commit into
masterfrom
DEV-1357_release_howto_hil
Oct 29, 2026
Merged

JongChern merged 1 commit into
masterfrom
DEV-1357_release_howto_hil

Conversation

@JongChern

Copy link
Copy Markdown
Contributor

DEV-1357 follow-up. This does for the C# release what ShimmerResearch/Shimmer-Java-Android-API#340 did for the Java one, and makes the hardware test gate the first thing a reader sees.

The change

PublishNuGet.yml header: it now opens with numbered "How to release" steps, laid out like Release Java API's:

  • Step 0 is the bench HIL (tools/hil/run-csharp-hil.ps1 -Report, which posts csharp-hil). It says the release does not proceed without it: the build job stops before building unless that status passed for the commit, or hil_waiver gives a Jira key.
  • Step 1 runs the workflow.
  • Step 2 tries the example VIs on a Shimmer3 and a Shimmer3R with the PR the run starts in Shimmer-Labview-API, then merges it. Merging publishes the LabVIEW release.

The old "Hardware test gate" paragraph at the bottom is folded into step 0. The pull-request line now also says PR runs skip the hardware test check, which they already did.

Run summary: the publish job now writes one, as the Java release does. It gives the release link, the NuGet packages, the hardware test result (or the waiver), and the next step: the LabVIEW PR to check and merge. update-labview's own summary, with the link to the LabVIEW run, follows it.

AGENTS.md: step 1 says the release does not proceed without csharp-hil. Step 3 says LabVIEW cannot run in CI.

Not changed

Tested

This PR's own build checks the workflow still parses. The new summary lines only run on a real release, so they get their first run at the next one.

🤖 Generated with Claude Code

PublishNuGet's header now opens with numbered "How to release" steps, as
Release Java API's does: step 0 is the bench HIL, without which the release
does not proceed (or a Jira key in hil_waiver), and the last step is trying
the example VIs on a Shimmer3 and a Shimmer3R before merging the LabVIEW PR,
which publishes the LabVIEW release. The old "Hardware test gate" paragraph
is folded into step 0.

The publish job now writes a run summary like the Java release's: the
release, the NuGet packages, the hardware test result, and the next step.
AGENTS.md says the same.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
@JongChern
JongChern merged commit 33ed2e6 into master Oct 29, 2026
5 checks passed
@JongChern
JongChern deleted the DEV-1357_release_howto_hil branch October 29, 2026 03:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant