- Web Changelog
- Android Changelog
- iOS Changelog
- React Native Changelog
- Flutter Changelog
- Segment iOS Changelog
- Segment Android Changelog
- Segment React Native Changelog
Understanding SDK changelog urgency and impact
Sprig SDK release notes use three related signals so you can decide whether and how soon to upgrade:
They often move together, but they are not the same. Recommended if you use names the feature this release fixes. 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:


- Recommended if you use — the feature this release fixes, shown under the version number when the release includes a fix.
- Upgrade urgency — Critical, High, or Low, shown once per release.
- Impact tag — security, behavior, or performance, shown on the change it affects.
Recommended if you use
This line appears on a release that includes a bug fix. It names the feature, question type, or integration this release fixes. If you use what it names, read the fix. If you do not, you can skip the release. A release that only adds a feature, or only upgrades a bundled SDK, leaves this line out. It has no fix for the line to name.
Pair it with urgency: the line tells you whether this release fixes a feature you use, and urgency tells you when to upgrade.
This line is published on fix releases from August 2026 onward. Older releases do not carry it, so for those, fall back to the change bullets.
Upgrade urgency
Every release has one urgency rating. If a release includes several changes, the rating reflects the most serious change in that release.Examples
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.Impact vs urgency
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.
Coming soon
An entry marked coming soon means the SDK version includes the feature, but Sprig has not turned it on for your account yet. Sprig turns it on after internal testing in production, and the rollout can take days or weeks.New features
Sprig releases new functionality frequently, upgrade when you want to take advantage of improvements:- Plain
add:entries (new question types and opt-in features) are usually Low, and they do not include a Recommended if you use line. - 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
- On releases newer than your current version, read Recommended if you use when it is present. You may skip a release when the fixed feature is not part of your setup.
- Read Upgrade urgency on the releases that remain.
- Skim Impact tags (security, behavior, performance) on the change bullets.
- Plan Critical/High upgrades into your next release window.