fix: remove auto-publish, make releases explicit

[dean0x]

Summary

• Deletes the broken .github/workflows/release.yml (triggered on GitHub release events, always failed at npm test)
• Removes the auto-publish release job from ci.yml — merging to main no longer triggers npm publish
• Adds new release.yml with workflow_dispatch trigger — releases are now explicitly requested from the GitHub Actions UI
• Updates CLAUDE.md release process docs

Closes #50

What changed

Before	After
ci.yml auto-published on merge to main when version changed	ci.yml only runs tests
Broken release.yml triggered on GitHub release events	New release.yml triggered manually via workflow_dispatch
Two competing release mechanisms (both broken in different ways)	One explicit release mechanism

Test plan

• PR CI passes (test job only)
• After merge: release.yml appears in Actions tab with "Run workflow" button
• Manual trigger: validates version, checks release notes, runs tests, publishes

[qodo-free-for-open-source-projects]

Review Summary by Qodo

Remove dead release.yml workflow

🐞 Bug fix

Walkthroughs

Description

• Removes broken .github/workflows/release.yml workflow
• Workflow triggered on GitHub releases but always failed at npm test
• ci.yml already handles publishing on push to main
• Resolves duplicate and non-functional release mechanism

Diagram

flowchart LR
  A["release.yml<br/>GitHub Release Trigger"] -->|"Deleted"| B["Removed<br/>Broken Workflow"]
  C["ci.yml<br/>Push to Main"] -->|"Remains Active"| D["Sole Publishing<br/>Mechanism"]

Loading

File Changes

1. .github/workflows/release.yml 🐞 Bug fix +0/-55

Delete non-functional release workflow file

• Entire workflow file deleted (55 lines removed)
• Workflow triggered on GitHub release publish events
• Contained npm test step that always failed (exits 1 by design)
• Duplicate of publishing logic already in ci.yml

.github/workflows/release.yml

---

[qodo-free-for-open-source-projects]

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)

Great, no issues found!

Qodo reviewed your code and found no material issues that require review

ⓘ The new review experience is currently in Beta. Learn more