Conversation
Deploying usesend with
|
| Latest commit: |
abd0864
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://bdd8bfc4.usesend.pages.dev |
| Branch Preview URL: | https://docs-changelog-1-9x.usesend.pages.dev |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
There was a problem hiding this comment.
Your free trial has ended. If you'd like to continue receiving code reviews, you can add a payment method here.
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
WalkthroughAdded a new March 2026 changelog entry (v1.9.0) to apps/docs/changelog.mdx documenting: campaign personalization using contact-book variables; configurable double opt-in confirmation flow and copy; expanded contact-book support in the SDK; dashboard analytics availability via public API and SDK; a public endpoint to delete campaigns; webhook multi-domain filtering; and other minor documentation edits. No exported or public code declarations were changed. Possibly related PRs
Suggested labels
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. 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 |
There was a problem hiding this comment.
🧹 Nitpick comments (1)
apps/docs/changelog.mdx (1)
10-18: Consider normalizing “contact book” terminology in this section.You use both “contact-book” (Line 10) and “Contact book” (Line 18). Standardizing this term in one style will make docs feel more polished and consistent.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@apps/docs/changelog.mdx` around lines 10 - 18, Normalize the "contact book" term to a single style across this section: change "contact-book variable registry" and "Contact book support" to the same form (e.g., "contact book" in lowercase as a two-word term) so usage is consistent; update both occurrences in the changelog section (the phrase "contact-book variable registry" and "Contact book support was expanded in the SDK") to the chosen style and scan the surrounding sentences in this block to ensure the same formatting is used everywhere.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Nitpick comments:
In `@apps/docs/changelog.mdx`:
- Around line 10-18: Normalize the "contact book" term to a single style across
this section: change "contact-book variable registry" and "Contact book support"
to the same form (e.g., "contact book" in lowercase as a two-word term) so usage
is consistent; update both occurrences in the changelog section (the phrase
"contact-book variable registry" and "Contact book support was expanded in the
SDK") to the chosen style and scan the surrounding sentences in this block to
ensure the same formatting is used everywhere.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 81e0cd1d-d4f6-4a49-8948-4cacdcaa95c0
📒 Files selected for processing (1)
apps/docs/changelog.mdx
Summary
v1.9.xchangelog section toapps/docs/changelog.mdxv1.9.0andv1.9.1(campaign personalization, double opt-in customization, broader API/SDK coverage, and multi-domain webhook filters)Testing
Summary by cubic
Add the March 2026 v1.9.0 changelog to
apps/docs/changelog.mdx, with expanded copy covering campaign personalization with contact-book variables, customizable double opt-in, broader API/SDK coverage (contact books, dashboard analytics, campaign deletion), and multi-domain webhook filtering.Written for commit ddbd86c. Summary will update on new commits.
Summary by CodeRabbit
New Features
Bug Fixes