Increased the CPU and memory allocation for DedupeHub in the Test environment and updated the release date for version 2.19.0 to the actual one.

[vlad-shapik]

• Increased the CPU and memory allocation for the DedupeHub container to 8 CPU and 40 GB in the Terraform deployment configuration to address memory overload issues during production location reindexing for the Test environment.
• Updated the release date for version 2.19.0 to the actual date: February 14, 2026.

[barecheck]

React App | Jest test suite - Code coverage report

Total: 40.47%

Your code coverage diff: 0.00% ▴

✅ All code changes are covered

[coderabbitai]

📝 Walkthrough

Walkthrough

Updated DedupeHub Fargate resource allocations in the Test environment (CPU: 4096 → 8192, memory: 8192 → 40960 MB) and updated release documentation: added Release 2.20.0 notes describing the architecture/env change and corrected a release date for v2.19.0.

Changes

Cohort / File(s)	Summary
Terraform Configuration deployment/environments/terraform-test.tfvars	Increased app_dd_fargate_cpu from 4096 to 8192 and app_dd_fargate_memory from 8192 to 40960.
Release Documentation doc/release/RELEASE-NOTES.md, doc/release/RELEASE-PROTOCOL.md	Added Release 2.20.0 notes documenting increased DedupeHub container resources for Test and updated v2.19.0 release date (Feb 13 → Feb 14, 2026); minor formatting adjustments and post-deploy step edits in RELEASE-NOTES.md.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• [OSDEV-2281] Upgraded DedupeHub memory and CPU allocation #821: Modifies the same app_dd_fargate_cpu and app_dd_fargate_memory variables across environment tfvars to increase DedupeHub resources.
• Increase DedupeHub fargate memory allocation for prod and pre-prod fron 16 GB to 30 GB #756: Updates DedupeHub Fargate resource settings and release notes with similar resource changes.
• Increased memory for the Dedupe Hub #419: Adjusts app_dd_fargate_memory for DedupeHub in other environment tfvars (Preprod/Prod), closely related to resource tuning.

Suggested reviewers

• roman-stolar
• VadimKovalenkoSNF
• mazursasha1990

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately summarizes the two main changes in the pull request: increased CPU/memory for DedupeHub and updated release date for v2.19.0.
Description check	✅ Passed	The description provides clear, relevant details about both main changes including specific resource allocations and the reasoning behind the DedupeHub upgrade.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch dedupehub-memory-cpu-upgrade

Tip

Issue Planner is now in beta. Read the docs and try it out! Share your feedback on Discord.

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[barecheck]

Dedupe Hub App | Unittest test suite - Code coverage report

Total: 55.73%

Your code coverage diff: 0.00% ▴

✅ All code changes are covered

[barecheck]

Countries App | Unittest test suite - Code coverage report

Total: 100%

Your code coverage diff: 0.00% ▴

✅ All code changes are covered

[barecheck]

Contricleaner App | Unittest test suite - Code coverage report

Total: 98.75%

Your code coverage diff: 0.00% ▴

✅ All code changes are covered

[barecheck]

Django App | Unittest test suite - Code coverage report

Total: 81.91%

Your code coverage diff: 0.00% ▴

✅ All code changes are covered

[VadimKovalenkoSNF]

LGTM

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@deployment/environments/terraform-test.tfvars`:
- Around line 48-49: The Fargate size variables
app_dd_fargate_cpu/app_dd_fargate_memory require the task definition to
explicitly set platform_version for 8 vCPU tasks: update the app_dd task
registration (the resource that currently has requires_compatibilities =
["FARGATE"]) to include platform_version = "1.4.0" (or later) so registration
won't fail, and then reconcile environment parity by either updating staging’s
app_dd_fargate_cpu/app_dd_fargate_memory from 4096/8192 to 8192/40960 or
document why staging should remain at the smaller size.

---

ℹ️ Review info

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d6a500c and 6fbc104.

📒 Files selected for processing (3)

• deployment/environments/terraform-test.tfvars
• doc/release/RELEASE-NOTES.md
• doc/release/RELEASE-PROTOCOL.md

🚧 Files skipped from review as they are similar to previous changes (2)

• doc/release/RELEASE-NOTES.md
• doc/release/RELEASE-PROTOCOL.md

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud