Release v2.1.0 — EU region support#24
Conversation
…ate publishing guide for automated CI releases
- bump to 2.1.0 (semver minor: EU region is a feature), CHANGELOG dated - fix region test asserting env-derived URL against hardcoded EU client (unblocks CI red on master since PR #23 merge) - biome-ignore for private-method bracket access in rest-client.test.ts - cherry-pick release hardening: Node >=20 engines, npm provenance, prepack build - remove protect-master.yml (unconditionally fails every master push; use branch protection settings instead) Verified locally: build, lint (biome exit 0), typecheck, 151 tests green with and without NEW_RELIC_REGION=EU. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012xEutmxJq5Ad1VdFyfzEhQ
|
Warning Review limit reached
Next review available in: 52 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the 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. 📝 WalkthroughWalkthroughThe release updates package versioning, npm packaging, publishing documentation, changelog entries, and REST client tests. It also removes the workflow that blocked direct pushes to ChangesRelease preparation
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
CHANGELOG.md (1)
24-47: 📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick winAdd all required Keep a Changelog sections to the 2.1.0 entry.
The entry currently shows only
Added,Changed, andFixed. Add emptyDeprecated,Removed, andSecuritysections in the standard order.Suggested structure
### Changed ... +### Deprecated + +### Removed + ### Fixed ... + +### Security +As per coding guidelines, every version entry must include
Added,Changed,Deprecated,Removed,Fixed, andSecuritysections.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@CHANGELOG.md` around lines 24 - 47, Add the missing Keep a Changelog sections to the 2.1.0 entry in CHANGELOG.md: include empty Deprecated and Removed sections between Changed and Fixed, and an empty Security section after Fixed, preserving the standard order Added, Changed, Deprecated, Removed, Fixed, Security.Source: Coding guidelines
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@PUBLISHING.md`:
- Around line 44-53: Update the manual publishing instructions in PUBLISHING.md
to avoid claiming provenance support from local npm publishing: remove
NPM_CONFIG_PROVENANCE=true from the fallback command or direct users to the
supported CI/OIDC workflow, and clearly label the local command as
non-provenance.
---
Outside diff comments:
In `@CHANGELOG.md`:
- Around line 24-47: Add the missing Keep a Changelog sections to the 2.1.0
entry in CHANGELOG.md: include empty Deprecated and Removed sections between
Changed and Fixed, and an empty Security section after Fixed, preserving the
standard order Added, Changed, Deprecated, Removed, Fixed, Security.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 1f9c7216-7099-4ede-9c50-387dea096177
📒 Files selected for processing (6)
.github/workflows/protect-master.ymlCHANGELOG.mdPUBLISHING.mdpackage.jsontest/client/rest-client/rest-client-requests.test.tstest/client/rest-client/rest-client.test.ts
💤 Files with no reviewable changes (1)
- .github/workflows/protect-master.yml
| ```bash | ||
| # Ensure package is built | ||
| npm ci | ||
| npm run build | ||
|
|
||
| # Test locally that it works | ||
| node dist/server.js | ||
|
|
||
| # Make bin executable | ||
| chmod +x dist/server.js | ||
| ``` | ||
|
|
||
| ### Add Shebang to Server | ||
| Edit `src/server.ts` and add at the very top: | ||
| ```typescript | ||
| #!/usr/bin/env node | ||
| ``` | ||
|
|
||
| Then rebuild: | ||
| ```bash | ||
| npm run build | ||
| ``` | ||
|
|
||
| ### Publish to NPM | ||
| ```bash | ||
| # Dry run to see what will be published | ||
| # optional dry run | ||
| npm publish --dry-run | ||
|
|
||
| # Publish for real | ||
| npm publish --access public | ||
| # publish (public package with provenance) | ||
| NPM_CONFIG_PROVENANCE=true npm publish --access public | ||
| ``` |
There was a problem hiding this comment.
🩺 Stability & Availability | 🟠 Major | ⚡ Quick win
Do not promise provenance from the manual local fallback.
NPM_CONFIG_PROVENANCE=true npm publish does not provide the supported cloud CI/OIDC context documented for npm provenance. Make the manual fallback explicitly non-provenance, or route it through the supported CI workflow. (docs.npmjs.com)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@PUBLISHING.md` around lines 44 - 53, Update the manual publishing
instructions in PUBLISHING.md to avoid claiming provenance support from local
npm publishing: remove NPM_CONFIG_PROVENANCE=true from the fallback command or
direct users to the supported CI/OIDC workflow, and clearly label the local
command as non-provenance.
- publish job on Node 24.x + npm@latest (OIDC needs npm >= 11.5.1) - drop NODE_AUTH_TOKEN from the publish step; auth comes from the Trusted Publisher config on npmjs.com (id-token: write already set) - provenance is automatic for OIDC publishes from public repos Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012xEutmxJq5Ad1VdFyfzEhQ
1 participant
Ships the EU region support that merged in #23 (2026-01-27) but never reached npm — closes the gap behind #20, where @karljv has been waiting since April for an npx-installable version.
What's in this release
NEW_RELIC_REGION(feat: Add regional support for EU/US regions with default fallback #23, @vksjangra) — closes EU Region unsupported #20chore/changelog-rules-governancebranch): Node >=20 engines, npm provenance,prepackbuildprotect-master.yml, which unconditionally fails every push to master (including PR merge commits) — replace with branch-protection settings[2.0.1] - TBDsection renamed and dated to match (the exact heading is whatscripts/extract-release-notes.mjskeys on)Verified locally
build, lint (biome: 0 errors), typecheck, and 151 tests green — both with and without
NEW_RELIC_REGION=EU.NPM_TOKENsecret dates to Aug 2025 (classic-token era, revoked by npm in Dec 2025). Either configure npm Trusted Publishing for this repo+workflow (preferred — CI already setsid-token: writeand provenance) or mint a fresh granular token and update the secret.npm publish --access public, tagsv2.1.0, and creates the GitHub Release from the CHANGELOG.After release
NEW_RELIC_REGION=EUon 2.1.0)🤖 Generated with Claude Code
https://claude.ai/code/session_012xEutmxJq5Ad1VdFyfzEhQ
Summary by CodeRabbit
New Features
NEW_RELIC_REGIONenvironment variable for regional configuration.Bug Fixes
Documentation
Chores