chore: bump to 2.1.0

[pandeymangg]

Release prep for #52.

Why minor, not patch

It adds a feature. Survey-interaction segment filters ("have seen X", "have completed X", …) did not work on iOS at all before — the SDK kept using the segment list it received at app launch, so a rule like "completed survey A → show survey B" never fired in the same session.

It changes behaviour for every app that upgrades, whether or not they use the feature. The user-state sync timer never fired: startSyncTimer() ran on URLSession's background delegate queue, and Timer.scheduledTimer installs on RunLoop.current, which has no run loop there. So user state was frozen for the whole session and only ever refreshed by the lazy check inside setup(). It now refreshes on expiry as intended — which means new periodic POST /user traffic that wasn't there before. That is the main thing to be aware of when rolling this out, and it's why patch would be the wrong signal: patch reads as "nothing to think about".

Workspaces that use interaction targeting also get an extra /user call after a display, response or finish, gated per survey and per event and debounced so a burst costs one request.

No public API changed. Every declaration the release touched is internal — verified there are no added public or open declarations in the diff. Nothing to migrate.

Changes

• FormbricksSDK.podspec: 2.0.0 → 2.1.0
• README.md: the two install snippets that name a concrete version

The podspec's s.source tag is derived from s.version, so the release tag needs to be 2.1.0 to match.

Verification

xcodebuild build passes. The full suite on main is 92 tests, 0 failures.

[coderabbitai]

Walkthrough

The podspec version changed from 2.0.0 to 2.1.0. The README now uses version 2.1.0 in the Swift Package Manager and CocoaPods installation examples.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'chore: bump to 2.1.0' directly and clearly describes the main change: updating the version to 2.1.0 in the podspec and README.
Description check	✅ Passed	The description is directly related to the changeset, explaining the version bump, the reasons for a minor version increment, and verification that tests pass.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

---

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.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@README.md`:
- Line 26: Update the CocoaPods example in the README code block so the
FormbricksSDK dependency uses a valid Podfile version requirement in the pod
declaration, and move any “or the latest version” wording out of the code sample
into surrounding prose. Keep the example anchored on the pod line itself and
ensure the snippet can be copied directly into a Podfile without syntax errors.

🪄 Autofix

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: da1eedcc-cb64-458e-8833-a97ddcc4cfd8

📥 Commits

Reviewing files that changed from the base of the PR and between 17c9b4e and f6ee78e.

📒 Files selected for processing (2)

• FormbricksSDK.podspec
• README.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