Pass the release flag as part of one options array

[JDS300]

The v0.4.0-rc.1 dispatch got all the way to publishing and then failed:

no matches found for `-`

Cause

Mine, from #15:

$flags = if ($prerelease) { @('--prerelease') } else { @('--latest') }
gh release create $tag @assets --repo $env:GITHUB_REPOSITORY @flags ...

PowerShell unrolls a single-element array returned from an if expression, so $flags was the string --prerelease, not an array. Splatting a scalar string is not splatting an array, and gh ended up with a bare -, which it tried to read as an asset filename.

The @assets splat in the same command works only because it always holds five elements and so never unrolls — which is exactly what made the pattern look safe to copy.

Fix

The flag joins the other options in one array that always holds at least six elements, so there is nothing that can unroll:

$options = @('--target', $env:GITHUB_SHA, '--title', ..., '--notes', ...)
if ($prerelease) { $options += '--prerelease' } else { $options += '--latest' }
gh release create $tag @assets --repo $env:GITHUB_REPOSITORY @options

+= on an array stays an array regardless of length, so the shape no longer depends on how many flags happen to be added.

What the failed run proved

It reached the publish step, so everything before it now works:

• the staged package verified byte-for-byte across a Linux-packaged zip and a Windows checkout — what Ship every file byte-for-byte, whatever platform packages it #16 fixed
• the tag/flag guard accepted v0.4.0-rc.1 without throwing
• all four build jobs and both artifact uploads succeeded

Nothing was published, so there is still no v0.4.0-rc.1 release or tag to clean up.

Verification

Release quality gate ALL PASS; workflow parses. The publish path cannot be executed anywhere but a real dispatch — there is no pwsh on this machine — so re-cutting the candidate is the test, as it was for this bug.

🤖 Generated with Claude Code