ci(release): pass publish-only through to the shared workflow

[BrianEstrada]

Why

The shared bun-npm-release workflow can now finish a release whose tag already exists (BrianEstrada/.github#4), for when npm rejects the publish after the release commit and tag are pushed. diffcop's v0.2.0 is in that state.

Approach

Adds a publish-only input to workflow_dispatch, passes it through, and pins the shared workflow to that merge commit (7127b39). Use it as gh workflow run release.yml --ref main -f version=X.Y.Z -f publish-only=true.

Verification

actionlint passes. The file is identical in diffcop and oxlint-deslopify.

[github-actions]

diffcop review

✅ All good

What we looked at

I read the full release.yml after the change. The new boolean publish-only input is passed through to the shared workflow, and the workflow pin moved to commit 7127b39. I found no bugs. I couldn't open the shared workflow, so I can't confirm that 7127b39 accepts a publish-only input.

Read (1): .github/workflows/release.yml

---

_{Reviewed a46eb2d · 10s · 1 tool call · 18.4K input tokens (78% cached) · 405 output · ~$0.02 run}