Release 4.5.0

[ali-farhadi-cko]

Release 4.5.0

Bumps Frames and Checkout to 4.5.0.

Changes since 4.4.0

• Risk SDK dependency updated from 4.0.1 to 6.0.1 (Update Risk SDK dependency to 6.0.1 #555)

Version bump

• Source/Core/Constants/Constants.swift
• Checkout/Source/Validation/Constants.swift
• Frames.podspec (version and pinned Checkout dependency)
• Checkout.podspec
• SPM sample project minimum version
• Sample app Podfile.lock files refreshed via pod install

Tag 4.5.0 has been pushed to the release branch and will be moved to the merge commit on main after merge.

🤖 Generated with Claude Code

[agent-wall-e]

🟡 Risk Classification: MINOR

Approval route: AI Review + Human Approval
Rollback controls: Staged rollout + rollback

Classification reasons

• no_low_class_matched
• prod_source_modified

Operational gates

• ✅ jira_ticket
• ✅ independent_review

Files analysed: 7

---

_{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
no_low_class_matched	informational	§2.2 (fall-through)	None of the deterministic Low classes (§2.2.3, §2.2.4, §2.2.7, docs-only) applied; classifier fell through to LLM evaluation.
prod_source_modified	informational	§2.1 M7 (informational)	At least one file is non-doc, non-test, non-IaC — i.e. application source code was modified.

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: Looks good to me

This PR still needs a human approval — wall-e cannot auto-approve it. For what it's worth, I read the diff and found nothing I'd block on.

This is a straightforward version bump from 4.4.0 to 4.5.0 across all version strings, podspecs, and lockfiles; everything is internally consistent.

What I checked

• All six files consistently update from 4.4.0 to 4.5.0 with no mismatches between podspecs, lockfiles, and Swift constants.
• The Frames.podspec pinned Checkout dependency is updated from 4.4.0 to 4.5.0, matching the new Checkout.podspec version.
• Both Podfile.lock files show updated checksums for Checkout and Frames, consistent with a pod install after the spec changes.
• The Risk dependency in the lockfiles already reflects ~> 6.0.1 (the stated change from 4.0.1), so no further lockfile changes are needed here.

---

_{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

[adrian-orlowski-cko]

LGTM