ci: drop Node 20 + add environment: production to publish job (fix OIDC)

[jaysin586]

What

Two CI fixes for this repo, bundled:

1. Drop Node 20 from the CI matrix (node-version: [20, 22, 24] → [22, 24] in npm-publish.yml + coveralls.yml). Node 20 is EOL and the pinned pnpm no longer supports it (ERR_PNPM_UNSUPPORTED_ENGINE). Keep 22 + 24.
2. Add environment: production to the publish job. The npm Trusted Publisher for @humanspeak/svelte-diff-match-patch is scoped to the production environment, but the publish-github-packages job did not declare it — so the OIDC token carried no matching environment claim and npm rejected the publish with ENEEDAUTH (run 28196102507). Every other repo in the fleet already sets this.

Note

main already has a Bump version to v0.1.3 commit from the failed run (the README ecosystem footer landed fine; only npm publish failed). The next successful publish will land as 0.1.4, skipping 0.1.3 on npm — harmless.

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

@jaysin586, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 8 minutes and 25 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

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

🚦 How do rate 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 see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: df1e8be6-cfa7-4dd3-8289-197062bd5541

📥 Commits

Reviewing files that changed from the base of the PR and between 413c46c and b81a9f9.

📒 Files selected for processing (2)

• .github/workflows/coveralls.yml
• .github/workflows/npm-publish.yml

---

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