Release: 2.26.1

[uc-brunosilva]

Release 2.26.1

Features

• Added support for US National (GPP) privacy framework
• Extended GPP API to Flutter, React Native and Unity bridges
• Exposed DPS metadata via new getDpsMetadata() API
• TCF resurfacing period now configurable via Admin UI (1–13 months)

Fixes

• Fixed TCF resurfacing period logic
• Fixed stored information not shown on DPS details
• Fixed TCF maintain legitimate interest logic on Deny All
• Fixed Android nullable type mismatch in setGPPConsent
• Fixed iOS Swift closure return type in GppData+Dict

🤖 Generated with Claude Code

[uc-brunosilva]

Code Review: PR #158 "Release: 2.26.1"

Target: PR #158 "Release: 2.26.1"
Files reviewed: 12
Verdict: No issues found

---

CI Validation

Check	Command	Status
Lint/Analyze	flutter analyze	PASS
Format	dart format --line-length=80 --set-exit-if-changed .	PASS — 0 changed
Tests	flutter test	PASS — 64 passed

---

No issues found on AI review by uc-code-review plugin using Claude Code.

[uc-brunosilva]

Code Review: PR #158 — bump/2.26.1

Target: PR #158 `bump/2.26.1`
Files reviewed: 13
Verdict: Suggestion

---

CI Validation

Check	Command	Status
Lint / Analyze	`flutter analyze`	PASS
Tests	Not configured	—

---

Issues

#	Title	Type	Where	Severity
1	`pod repo update` adds significant CI runtime overhead	Architecture	`.github/workflows/ci.yml:188`	suggestion

---

1. `pod repo update` adds significant CI runtime overhead

Type: Architecture | Severity: suggestion | Where: `.github/workflows/ci.yml:188`

`pod repo update` performs a full sync of the CocoaPods spec repository, which typically adds 5–10 minutes to every CI run. This is a blunt fix for a CDN cache staleness issue that is specific to the 2.26.1 release window — once the CDN propagates fully, the step becomes permanently wasteful overhead on every future build.

A targeted alternative is to use `pod install --repo-update` only on the `flutter build` step, or to scope the workaround to a time-limited flag that can be removed after the CDN settles. If the CDN issue is already resolved, remove this step.

# Option A: remove the step once CDN has propagated (preferred)
# Delete the "Update CocoaPods repo" step entirely.

# Option B: if the update is still needed, scope it to pod install only
- name: Build
  working-directory: ./example
  run: flutter build ios --debug --no-codesign --simulator
# and replace pod repo update with:
- name: Pod install with repo update
  working-directory: ./example/ios
  run: pod install --repo-update

---

Reviewed by uc-code-review plugin using Claude Code.