What is the problem or goal you're trying to solve or accomplish?
The customer is on the Professional tier and depends on their reports working reliably. They want to know about significant product changes before those changes reach their workspace, so they can prepare and protect reports that already work.
Today they can't use the public Changelog (docs.preset.io/docs/update) for this. The latest entry is Sep 2, 2026 (v6.0.0.32), but their workspace is running v6.1, which has no changelog entries. The page also doesn't separate releases by plan tier, so they can't tell which entries apply to them or what version they should expect to be on. As a result, they don't consider the changelog trustworthy as a record of what changed in their environment.
In the customer's words: "Is there a way you can notify us before making big changes? We want our reports to work without issues and to be prepared to keep separate instances to prevent any new big change you make from affecting the reports that already work well."
How are you solving it currently?
They have no reliable way to do this today. They find out about changes after deployment, when something behaves differently in their reports, and then raise a support ticket. Support pointed them to the public Changelog, but it doesn't cover the version they are running. They have no advance-notice channel and no way to confirm which version or changes apply to their tier.
What is your recommended solution?
Publish three separate changelogs, one per plan tier (Free/Starter, Professional, Enterprise). Each should reflect the versions actually deployed to that tier and be kept current with each release, so customers can trust it as an accurate record of what changed in their own workspace.
The customer also asked for advance notification before significant changes are rolled out to their workspace. They also want the option to keep a separate instance on the current behavior, so that existing reports aren't affected by a major change before they have validated it.