> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sprig.com/llms.txt
> Use this file to discover all available pages before exploring further.
# SDK Changelog
Explore records of changes made to your specific Sprig SDK platform, including bug fixes, new features, etc.
Changelogs:
1. [Web Changelog](/docs/developer-center/sdk-changelog/web-changelog)
2. [Android Changelog](/docs/developer-center/sdk-changelog/android-changelog)
3. [iOS Changelog](/docs/developer-center/sdk-changelog/ios-changelog)
4. [React Native Changelog](/docs/developer-center/sdk-changelog/react-native-changelog)
5. [Flutter Changelog](https://pub.dev/packages/sprig_flutter_plugin/changelog)
6. [Segment iOS Changelog](https://github.com/UserLeap/analytics-swift-sprig/releases)
7. [Segment Android Changelog](https://github.com/UserLeap/analytics-kotlin-sprig/releases)
8. [Segment React Native Changelog](https://github.com/UserLeap/analytics-react-native-plugin-sprig/releases)
## Understanding SDK changelog urgency and impact
Sprig SDK release notes use three related signals so you can decide whether and how soon to upgrade:
| Signal | Answers | Where it appears |
| :- | :- | :- |
| **Recommended if you use** | Does this release affect me at all? | Once per release, directly under the version number (August 2026 onward) |
| **Upgrade urgency** | How soon should I upgrade? | Once per release |
| **Impact** | What happens if I stay on the old version? | On meaningful change bullets, and as a short summary on higher-urgency releases |
They often move together, but they are not the same. **Recommended if you use** describes who is affected. **Impact** describes the blast radius. **Urgency** describes when to act.
New features appear frequently. A new feature alone does **not** usually mean you must upgrade.
Here is where each signal appears on an SDK changelog:
1. **Recommended if you use** — who the release applies to, shown under the version number.
2. **Upgrade urgency** — Critical, High, or Low, shown once per release.
3. **Impact tag** — security, behavior, or performance, shown on the change it affects.
### Recommended if you use
Releases carry one **Recommended if you use** line under the version number, naming the features, question types, or integration surfaces that release touches. It is a filter, not a rating: if nothing in that line is part of your setup, the release almost certainly does not need your attention.
| Example line | Read it as |
| :- | :- |
| **Recommended if you use:** Session Replay | Only relevant if you have Session Replay enabled |
| **Recommended if you use:** Carry Forward, Validated Text questions, or Feedback studies | Relevant if any one of the three applies to you |
| **Recommended if you use:** Session Replay in SwiftUI apps on iOS 26 or later | Narrowed to a platform and integration method, not just a feature |
| **Recommended if you use:** all customers | No filtering; everyone should upgrade |
Pair it with urgency: the line tells you **whether** a release applies, and urgency tells you **when** to act on it.
This line is published on releases from August 2026 onward. Older releases do not carry it, so for those, fall back to the change bullets and impact tags.
### Upgrade urgency
Every release has one urgency rating. If a release includes several changes, the rating reflects the **most serious** change in that release.
| Urgency | Meaning | What you should do |
| :- | :- | :- |
| **Critical** | Security exposure; data loss or corruption; crash; a generally available feature fully broken | Upgrade as soon as practical |
| **High** | Incorrect survey logic or progression; host-app or host-page regression; a major feature broken for many customers | Upgrade in your next planned release window |
| **Low** | Visible defects with a workaround or a narrow blast radius; polish; opt-in or coming-soon features | Upgrade when convenient |
#### Examples
| Change | Urgency | Why |
| :- | :- | :- |
| XSS prevention on Button URLs | Critical | Security exposure |
| Consent/legal or Skip Logic evaluation corrected | High | Wrong questions may have been shown; collected responses may be affected |
| SDK overwrites host page body background | High (web embeds) | Can break styling on your site |
| Dependency updates with no practical embed exposure | Low | Hygiene; low need to act immediately |
### Impact tags
Impact tags highlight changes that affect **behavior, data quality, security, host integration, or noticeable performance**. Most changelog bullets have **no** impact tag. That usually means polish or presentation.
| Tag | Means the change involves… | Example |
| :- | :- | :- |
| `[impact: security]` | XSS, CSP, embed isolation, or actionable security dependency fixes | Prevent XSS for Button URLs |
| `[impact: behavior]` | Wrong survey flow; missing or wrong questions; response capture; host-app or host-page breakage; crashes | Consent/legal Skip Logic correction |
| `[impact: performance]` | Replay/heatmap performance, memory, battery, extra network calls, or UI freezes | Duplicate replay captures prevented |
| *(no tag)* | Spacing, alignment, hover states, copy, or presentation | Alignment of selection boxes in Multiple Choice |
Some releases also include a one-line **Impact** summary, for example:
**Impact:** Surveys with Skip Logic could advance incorrectly. This release corrects evaluation for consent/legal and Multiple Choice logic.
That sentence is written for **Critical**, **High**, and **Low** releases.
### Impact vs urgency
| | **Impact** | **Urgency** |
| :- | :- | :- |
| Question | What happens if I don’t upgrade? | How soon should I upgrade? |
| About | Nature of the change and the blast radius | When to act |
| Values | security / behavior / performance / none | Critical / High / Low |
The same change can matter differently depending on how you use the SDK:
* A body-background fix may be **High** for web page embeds, but less urgent inside a native WebView.
* A self-host packaging change may be **High** for customers who mirror SDK assets, and **Low** if you load from the Sprig CDN.
### New features
Sprig releases new functionality frequently, upgrade when you want to take advantage of improvements:
* Plain `add:` entries (new question types, capabilities marked coming soon, features you must enable) are usually **Low**.
* Upgrade for a feature when *you* want that capability, the timeline is up to you.
* If a release mixes a new feature with a meaningful fix, follow the **urgency** and **impact** of the fix.
### How to use this when upgrading
1. Scan **Recommended if you use** on releases newer than your current version, and skip the ones that name nothing you use.
2. Read **Upgrade urgency** on the releases that remain.
3. Skim **Impact tags** (security, behavior, performance) and the Impact summary on Critical and High releases.
4. Plan **Critical/High** upgrades into your next release window.