ci: keep every pending release in the queue

[altaywtf]

Summary

A late release run no longer replaces a newer one waiting in the release group, so a releasable push to main can't sit unreleased until the next push.

Step	Before: one pending slot	After: queue: max
Newer push B's verify finishes first	B's release waits	B's release waits
Older push A's verify finishes	A's release replaces B's	A's release waits behind B's
Release group frees up	A skips because main moved on; B waits for the next push	B releases, then A skips

• The release job now uses queue: max. Actionlint 1.7.12 doesn't know the key yet, so .github/actionlint.yaml ignores that one error for ci.yml only.
• The release checkout sets no ref, which on a push already checks out github.sha; unchanged.

Verification

• pnpm verify
• pnpm verify:full
• Actionlint 1.7.12 and Zizmor 1.30.1 are clean. Without the ignore, actionlint fails on the queue key; a queue key in any other workflow still fails.

Review Notes

• Package, deploy, or release impact: a ci: commit releases nothing, and deploy.yml doesn't run for these paths.
• Follow-up work: none.

---

Written by an agent (Claude Code, Claude Opus 5.5)

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.