fix(release): publish GitHub releases without npm

[CoreyLeath-code]

Summary

Repairs the main-branch Release workflow by making semantic-release publish GitHub Releases only. It no longer attempts the default npm publishing path, which is not configured for this Python service.

Files changed

• package.json — explicitly configures semantic-release with commit analysis, release notes, and GitHub publishing plugins; deliberately excludes @semantic-release/npm.
• .github/workflows/release.yml — grants the GitHub Release permissions semantic-release needs and checks out full history so release analysis can see prior tags and commits.

Validation performed

• Confirmed the repository release metadata exists in package.json.
• Confirmed the workflow is limited to main pushes and uses the repository GITHUB_TOKEN; no external npm token is introduced.
• Standard repository CI is running for this PR. The actual Release workflow will execute only after this correction reaches main.

Risks

• This change intentionally stops npm package publishing. The repository is a Python service and has no npm publishing configuration or registry credential.
• A GitHub Release is still created only when semantic-release determines that commit history warrants a version.

Follow-up recommendations

• Add a release-workflow dispatch or dry-run validation path if pre-merge semantic-release execution becomes necessary.
• Add conventional-commit enforcement if automated versioning is expected for every release.

[coderabbitai]

Warning

Review limit reached

@CoreyLeath-code, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 40 minutes

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

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: a0c7bfb0-dec9-4066-8e67-57fcc70b38a1

📥 Commits

Reviewing files that changed from the base of the PR and between 22984c8 and 46aa711.

📒 Files selected for processing (2)

• .github/workflows/release.yml
• package.json

---

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.}