chore: upgrade lottie-ios to ~> 4.5.0

[mhamann]

Upgrades the lottie-ios dependency from ~> 4.3.3 to ~> 4.5.0 in both the podspec and Package.swift.

This resolves a peer dependency conflict for React Native consumers using lottie-react-native 7+, which requires lottie-ios 4.5.0.

Changes:

• Rownd.podspec: lottie-ios ~> 4.3.3 → ~> 4.5.0
• Package.swift: .upToNextMajor(from: "4.3.3") → .upToNextMajor(from: "4.5.0")

Note: Version bump left for release-it to handle during release.

Summary by Sourcery

Build:

• Bump the Lottie iOS dependency from 4.3.3 to 4.5.0 in Package.swift and the CocoaPods podspec to align supported versions.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This PR bumps the lottie-ios dependency to version 4.5.0 across both Swift Package Manager and CocoaPods manifests to align with lottie-react-native 7+ requirements, without changing any app/runtime logic.

File-Level Changes

Change	Details	Files
Update Swift Package Manager dependency constraint for Lottie to start from version 4.5.0 instead of 4.3.3.	Adjust the .upToNextMajor(from:) version for the Lottie package to 4.5.0 in the Package.swift manifest Keep all other package dependencies and configuration unchanged	Package.swift
Update CocoaPods dependency constraint for lottie-ios to ~> 4.5.0 instead of ~> 4.3.3.	Change the lottie-ios dependency version requirement in the podspec to ~> 4.5.0 Leave all other podspec metadata and dependencies as-is	Rownd.podspec

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[qodo-code-review]

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
🟢	No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
⚪	🎫 No ticket provided Create ticket/issue
Codebase Duplication Compliance
⚪	Codebase context is not defined Follow the guide to enable codebase context checks.
Custom Compliance
🟢	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Meaningful Naming and Self-Documenting Code Objective: Ensure all identifiers clearly express their purpose and intent, making code self-documenting Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Robust Error Handling and Edge Case Management Objective: Ensure comprehensive error handling that provides meaningful context and graceful degradation Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Error Handling Objective: To prevent the leakage of sensitive system information through error messages while providing sufficient detail for internal debugging. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Logging Practices Objective: To ensure logs are useful for debugging and auditing without exposing sensitive information like PII, PHI, or cardholder data. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Security-First Input Validation and Data Handling Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent vulnerabilities Status: Passed Learn more about managing compliance generic rules or creating your own custom rules

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

[sourcery-ai]

Hey - I've reviewed your changes and they look great!

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[qodo-code-review]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
General	Align dependency version constraints To ensure consistent dependency resolution, change the Lottie version constraint in Package.swift from .upToNextMajor to .upToNextMinor to match the more restrictive constraint in Rownd.podspec. Package.swift [61] -.upToNextMajor(from: "4.5.0") +.upToNextMinor(from: "4.5.0") Apply / Chat Suggestion importance[1-10]: 7 __ Why: The suggestion correctly identifies a version constraint mismatch between Package.swift (SwiftPM) and Rownd.podspec (CocoaPods), which could lead to dependency issues. Aligning them improves project stability.	Medium
More