Skip to main content
Upgrade from: the latest 6.0 patch. Skipping 6.0 is not supported; see Upgrade paths. Downtime: a maintenance window. Applies to: all editions and setups.

What changes

  • Survey visibility: organizations can restrict who sees each survey and its responses. It’s off until you turn it on.
  • Encrypted single-use links created before 6.1 stop working and must be created again.
  • The permission schema changes, so permission preparation is needed.
  • New database indexes are built, and Embedded Data and survey ownership are backfilled during the migration.
  • Some API requests are validated more strictly (see integration changes).

Before you upgrade

Patch actions

Check each patch you cross. You can go straight to the latest 6.1 patch.

Upgrade

Follow the runbook for your setup: Kubernetes, Docker Compose or one-click. Because the permission schema changes, permission preparation asks you to confirm the change. See schema changes in permission preparation.

Check it worked

  • Users can sign in, including existing SSO users, and see the surveys they should.
  • You can submit a survey response, and API keys work for what they’re allowed to do.
  • Webhooks and workflows run, and dashboard charts load.
  • Old and new file uploads open.
  • Then create new encrypted single-use links, and turn on survey visibility if you want it.
Also do the checks after the upgrade.

If something goes wrong

Keep the maintenance window open. If you can’t fix the problem, restore the app database, Hub data, SpiceDB and your configuration from the backup; see backup and restore. Don’t go back to an older version just to make old single-use links work again: that reopens the security issue 6.1 fixes.

Integration changes requiring action

6.1 is a minor release, but these changes can affect existing integrations. API
  • Ending-card URLs need a real host. buttonLink and url on ending cards (v1, v2 and v3 survey create and update) must use a hostname with a dot (intranet.example.com), localhost or an IP address. A host like http://intranet now returns 400. Existing surveys keep loading; the rule applies when they are next saved (#9399)
  • Hidden fields can’t share a name with a question. Adding one on POST or PUT /api/v1/management/surveys returns 400. Existing surveys keep saving (#9467)
  • New survey limit per workspace. SURVEY_WORKSPACE_LIMIT (a number, default 10000, archived surveys included) caps the surveys in one workspace. Creating or copying a survey past it returns 422 workspace_survey_limit_reached on v1 and v3. Raise it before upgrading if a workspace is close (#9412)

More 6.1 changes

See the release notes for each 6.1 patch.