Add residential sub-object to anonymizer for Insights#410
Conversation
The web service now nests a `residential` object inside `ip_address .anonymizer`, sourced from the full-feed GeoIP Residential Proxy database. This is exposed automatically via the geoip2 dependency's new `Anonymizer.residential` attribute (a `geoip2.records .AnonymizerFeed`), so no model changes are needed here. Update the test fixtures and assertions to cover the new field, and note the change and the geoip2 5.3.0 minimum in HISTORY.rst. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
Warning Review limit reached
Next review available in: 59 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. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (5)
✨ 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 |
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request adds support for the residential attribute within the ip_address.anonymizer object, which represents residential proxy data. The changes include updating mock JSON response files and adding corresponding assertions in the test suite (test_models.py and test_webservice.py). The changelog has also been updated to document this feature. There are no review comments, so I have no feedback to provide.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
1 participant
Summary
Surfaces the new
residentialsub-object of theanonymizerobject in the minFraud Insights and Factorsip_addressresponse. The models reuse the GeoIP2 library's Anonymizer record, so this is a fixtures/tests/changelog change; the field flows through via the dependency.Depends on maxmind/GeoIP2-python#440. At release time the
geoip2requirement must be bumped to>=5.3.0once that version is on PyPI.Testing
With geoip2 built from that PR: pytest 246 passed; ruff check, ruff format --check, and mypy clean. Against released geoip2 5.2.0 the new assertions fail as expected.
🤖 Generated with Claude Code