Skip to content

Check the Windows launcher before each release, not on every pull request - #92

Merged
jadamcrain merged 1 commit into
mainfrom
windows-launcher-at-release
Oct 15, 2026
Merged

jadamcrain merged 1 commit into
mainfrom
windows-launcher-at-release

Conversation

@jadamcrain

Copy link
Copy Markdown
Member

cli (windows-latest) builds the CLI zip on Windows and checks its launcher (bin\dnp3c.cmd): it runs with Java 21, also from a JAVA_HOME with spaces, and rejects Java 11 and a missing Java. The launcher hasn't changed since the first commit, but every pull request and merge-queue run waited on this job, the slowest and so far the flakiest.

  • Release: a windows-launcher job runs the same check when a tag is pushed, and the release job needs it, so a broken launcher stops the release before anything is published to Maven Central.
  • CI: cli (ubuntu-latest) stays, building the zip and checking the Linux launcher on every pull request.
  • CLAUDE.md: the releasing section mentions the Windows check.

main's required checks need cli (windows-latest) removed, or the merge queue waits for a check that no longer runs.

@jadamcrain
jadamcrain enabled auto-merge October 15, 2026 20:47
@jadamcrain
jadamcrain added this pull request to the merge queue Oct 15, 2026
Merged via the queue into main with commit 630dc64 Oct 15, 2026
4 checks passed
@jadamcrain
jadamcrain deleted the windows-launcher-at-release branch October 15, 2026 21:37
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