feat: auto-merge release-please PRs and auto-publish to npm

[terry90918]

Summary

• The release chain (merge feature PR → merge release-please PR → `npm publish`) had two manual steps that were routinely forgotten.
• `main` now requires the `Lint, Format, Tests` check to pass before merge (added branch protection — no review requirement, admin override still allowed).
• `release.yml` requests GitHub auto-merge on the release-please PR right after it's opened/updated.
• Once that PR merges, the same workflow's `publish` job runs `npm publish --access public` (gated on release-please's `release_created` output), using a new `NPM_TOKEN` repo secret.
• Updated `CLAUDE.md`'s Publishing section to describe the new automated flow.

Effect

Going forward, merging a fix/feat PR into `main` is the only manual step — release-please, the release PR merge, and npm publish all happen automatically.

Test plan

• Verified `main` branch protection: required status check = `Lint, Format, Tests`, no PR review requirement, admin override enabled
• Verified `NPM_TOKEN` secret exists on the repo
• First real release-please PR after this merges will be the live end-to-end test of auto-merge + auto-publish

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 1 minute

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

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: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 35eb9e52-59f9-4f46-a936-7059c765a973

📥 Commits

Reviewing files that changed from the base of the PR and between ed84b1f and ea32d60.

📒 Files selected for processing (2)

• .github/workflows/release.yml
• CLAUDE.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch develop

---

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

[Copilot]

Pull request overview

Automates the release pipeline for @jurislm/coolify-mcp by requesting GitHub auto-merge for Release Please PRs and publishing to npm from CI, and documents the updated publishing flow.

Changes:

• Update release.yml to (1) enable auto-merge on the Release Please PR and (2) run npm publish --access public when a release is created.
• Update CLAUDE.md to describe the new fully automated release flow and required repo secret.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
CLAUDE.md	Documents the new automated “release PR auto-merge + npm publish” flow.
.github/workflows/release.yml	Requests auto-merge on the release PR and conditionally publishes to npm on release creation.