Merge release/4.5.0 into develop

[ali-farhadi-cko]

Back-merge of the 4.5.0 release branch into develop to keep Gitflow in sync, as per the release process.

Release PR: #556

🤖 Generated with Claude Code

[agent-wall-e]

🔴 Risk Classification: MAJOR

Approval route: AI Review + Human Approval Required
Rollback controls: Change-freeze window + documented rollback plan

Classification reasons

• security_sensitive_path:.github/workflows/check-pr.yml
• security_sensitive_path:.github/workflows/codeql-analysis.yml
• security_sensitive_path:.github/workflows/deploy-github-pages.yml
• security_sensitive_path:.github/workflows/generate-jazzy-docs.yml
• security_sensitive_path:.github/workflows/publish-Checkout.podspec.yml

Operational gates

• ✅ jira_ticket
• ✅ independent_review

Files analysed: 100

---

_{wall-e 2026.06.19-02 · policy 6b4ce2b3b45a…}

[agent-wall-e]

🔬 Debug — why this classification?

Each reason code emitted by the classifier, its source clause in the AI in SDLC Control Framework, and what it means.

Reason code	Kind	Clause	Meaning
security_sensitive_path — .github/workflows/check-pr.yml	classifying	§2.1 M4/M5	Path matched a sensitive pattern (auth, secrets, crypto, PCI, migrations, network IaC).
security_sensitive_path — .github/workflows/codeql-analysis.yml	classifying	§2.1 M4/M5	Path matched a sensitive pattern (auth, secrets, crypto, PCI, migrations, network IaC).
security_sensitive_path — .github/workflows/deploy-github-pages.yml	classifying	§2.1 M4/M5	Path matched a sensitive pattern (auth, secrets, crypto, PCI, migrations, network IaC).
security_sensitive_path — .github/workflows/generate-jazzy-docs.yml	classifying	§2.1 M4/M5	Path matched a sensitive pattern (auth, secrets, crypto, PCI, migrations, network IaC).
security_sensitive_path — .github/workflows/publish-Checkout.podspec.yml	classifying	§2.1 M4/M5	Path matched a sensitive pattern (auth, secrets, crypto, PCI, migrations, network IaC).
security_sensitive_path — .github/workflows/publish-Frames.podspec.yml	classifying	§2.1 M4/M5	Path matched a sensitive pattern (auth, secrets, crypto, PCI, migrations, network IaC).
security_sensitive_path — .github/workflows/run-regression-tests.yml	classifying	§2.1 M4/M5	Path matched a sensitive pattern (auth, secrets, crypto, PCI, migrations, network IaC).
security_sensitive_path — .github/workflows/validate-for-app-store.yml	classifying	§2.1 M4/M5	Path matched a sensitive pattern (auth, secrets, crypto, PCI, migrations, network IaC).
security_sensitive_path — Checkout/Source/Tokenisation/CheckoutAPIService.swift	classifying	§2.1 M4/M5	Path matched a sensitive pattern (auth, secrets, crypto, PCI, migrations, network IaC).
security_sensitive_path — CheckoutTests/Tokenisation/CheckoutAPIServiceTests.swift	classifying	§2.1 M4/M5	Path matched a sensitive pattern (auth, secrets, crypto, PCI, migrations, network IaC).

Kinds:

• classifying — this rule contributed to the chosen tier.
• informational — context only; did not by itself decide the tier.

See issue #3 for the proposal to formalise this map as Appendix A of the standards doc.

_{wall-e 2026.06.19-02 · debug}

[agent-wall-e]

🔵 Advisory review: Sound, but needs your judgement

This PR needs a human approval. The code itself reads as correct; whether it should land depends on context I don't have.

This is a Gitflow back-merge of release/4.5.0 into develop, bringing in Risk SDK integration, iOS 13+ minimum target, Xcode 26.x CI infrastructure, and a baseURLPrefix extension. The change is technically substantial and mostly correct, but several items warrant human review before landing.

For you to decide

• The Risk SDK integration in CheckoutAPIService.swift uses a 5-second timeout (timeoutInterval: 5.0) via taskCompletionQueue and isTaskCompleted flag — the timeout recovery logic is truncated in the diff, so it cannot be fully verified; the reviewer should confirm the DispatchWorkItem/timer implementation is race-free and that isTaskCompleted is only ever accessed on taskCompletionQueue.
• The branch-guard check in publish-Checkout.podspec.yml and publish-Frames.podspec.yml has been entirely commented out, meaning those workflows can now be triggered from any branch; this is an operational policy decision, not just a code correctness issue.
• The run-regression-tests.yml trigger was changed from pull_request: [labeled] to workflow_dispatch only, removing automated regression runs on labeled PRs — this is a deliberate workflow change whose operational impact the team should confirm is intentional.
• The SPM sample project pin was changed from upToNextMajorVersion: 4.0.0 to exactVersion: 4.3.6, which means the sample will not automatically consume 4.5.0 unless manually updated — this looks like an oversight given the rest of the release bumps to 4.5.0.
• The PrivacyInfo.xcprivacy uses non-standard strings ('Device Model', 'SDK Version', 'SDK Lifecyle Events' [sic]) as NSPrivacyCollectedDataType values; Apple requires specific enumerated keys from their approved list, so these entries may cause App Store submission issues.
• The Checkout.podspec now declares s.dependency 'Risk', '~> 6.0.1', making Risk a transitive CocoaPods dependency for all Checkout SDK consumers — this is a breaking behavioral change for integrators who may not expect a fingerprinting/device-ID SDK to be pulled in automatically.
• The CHANGELOG.md inserts entries for 4.3.2 through 4.3.8 above the existing 4.3.1 entry (i.e., in descending order), which is correct, but 4.5.0 itself does not appear to be added to the changelog in this diff — a reviewer should verify it was added elsewhere or is expected to be added separately.
• The #warning annotation left on the commented-out Apple Pay integration test (test_createApplePayToken) will emit a build warning in every build until resolved; this is a concrete gap in test coverage that the team should track.

⚠️ The diff was too large to read in full, so this review covers only part of the change.

---

_{This is not an approval. wall-e cannot auto-approve this PR — it is an opinion to help whoever does. Advisory review · us.anthropic.claude-sonnet-4-6 · wall-e 2026.06.19-02}

[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