Release Notes
Track meaningful product updates with enough context to plan adoption, align stakeholders, and reduce rollout friction.
How to use this changelog
Review each release through an operational lens: identify what changed, which teams are affected, and whether onboarding or documentation updates are needed.
For high-impact updates, schedule a short internal review before enabling changes across all workspaces.
v2.6
2026-02-04
• Introduced interaction logic snapshots for easier approval workflows
• Improved publish performance for large prototype projects
• Expanded analytics payload options for page-level attribution
v2.5
2026-01-16
• Added template branching support for multi-persona onboarding
• Released updated API webhooks for review-state transitions
• Improved doc search indexing and page relevance
v2.4
2025-12-18
• Launched shared decision log exports
• Added workspace-level reviewer permissions
• Refined keyboard and screen reader support across editors
Next steps after each release
Release adoption workflow
Treat each release as an operational change event. Teams that absorb updates well usually run one short adoption cycle with explicit ownership and success signals.
Recommended sequence: identify affected workflows, review changed behavior in staging, align customer-facing messaging, and update measurement assumptions before broad rollout.
For higher-risk updates, assign one accountable owner to coordinate product, design, and engineering decisions so late-stage ambiguity does not create avoidable rework.
Related resources
Use these resources alongside release notes:
- • Implementation docs for setup and workflow specifics.
- • Guides for role-based execution playbooks.
- • Media kit for approved external messaging assets.