ci: create a GitHub release when publishing a tag

[robertn702]

Tag pushes published to npm but never created a GitHub release, so the Releases page stopped at v0.6.0. The publish job now creates the release with the tag's CHANGELOG section as notes and the packed tarball attached. It skips if the release already exists and fails if the changelog has no section for the version.

[coderabbitai]

Warning

Review limit reached

Next included review available in 52 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Advanced

Run ID: 35a8fd31-2d04-4822-acb8-c539950988e2

📥 Commits

Reviewing files that changed from the base of the PR and between 8077927 and 9b17a4b.

📒 Files selected for processing (1)

• .github/workflows/publish.yml

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}