This page covers which releases get fixes. Response times, recovery targets and other support commitments
for Enterprise customers are defined in your contract, not here.
Versioning
Formbricks follows Semantic Versioning:Major.Minor.Patch, for example 6.2.1.
Every release is published on GitHub Releases with its
release notes. Each release states its upgrade impact: None, or Action required with the steps.
Patch releases
Patch releases are backward compatible. They contain bug fixes and security fixes only. They add no new features and don’t change APIs. They normally contain no database migrations. If a security fix needs a small change in behavior, or a new optional setting such as an environment variable, the release notes say so under Upgrade impact: Action required.Upgrade path
Upgrade one minor version at a time, always to its latest patch. Skipping a minor version is not supported. Within a minor version you can go straight to its latest patch. See Upgrade paths.Integration compatibility
Patch and minor releases preserve supported SDK and stable public API integrations within the same Formbricks major version. You do not need to rewrite a supported integration for a routine patch or minor upgrade. Breaking changes to that contract require a major release and migration guidance.- Existing documented requests, response fields and SDK behavior remain compatible. New features may require a newer SDK; see SDK compatibility.
- API versions and SDK package versions are independent of the Formbricks app version. Beta and private-beta interfaces carry their stated stability limits.
- If an urgent security fix must change existing behavior, its release notes identify the exception, affected versions and required action. Historical exceptions remain documented in the version pages.
Maintained Versions
Each minor release is maintained for three calendar months, starting on the day its first stable version is published. Release candidates and the date you installed it do not count. If the ending month has no matching day, support ends on the last day of that month: a minor published on November 30 is maintained through the last day of February.- Patch releases do not restart the clock.
6.2.3ends support on the same day as6.2.0. - A newer minor does not shorten the window of an older one. This is a time window, not a cap on the number of maintained versions.
- The support-end date of each minor is published in its release notes. Support runs through the end of that day.
A maintained minor is not a frozen version. To stay covered, install its patch releases as they are
published.
Security Fixes
- High and Critical vulnerabilities (validated CVSS v4.0 base score of 7.0 or higher) are fixed on every maintained minor. A public CVE is not required.
- Lower-severity vulnerabilities are fixed in the latest minor only. Active exploitation, or a credible attack chain with serious impact on customers, gets an expedited review regardless of score.
- Dependency vulnerabilities follow the same rules. A scanner match alone does not mean a release is affected; we verify whether the vulnerable code path is reachable in Formbricks.
- If a fix cannot be safely backported to an older minor, we publish a mitigation or upgrade guidance for it instead.
Bug Fixes
Non-security bug fixes ship in the latest minor only. Older minors receive security fixes only, even when a bug is blocking for you. To receive a bug fix, upgrade to the latest minor.End of Support
After its support-end date, no new fixes are accepted for a minor. Upgrade to a maintained minor to stay covered. A security fix accepted for backport before the end date is still completed and published, even if the work finishes after it.Upgrade Recommendations
- Run the latest stable release. It is the only version that receives every fix.
- Pin a release tag in production instead of a moving tag such as
latest. - Upgrade one minor version at a time. Read its version page and the upgrade impact of each patch you cross, then follow the upgrade procedure.
- Plan to move to a newer minor before your current one reaches its support-end date.