Changelog and Release Notes
A complete, searchable history of every Workexe release since v1.0, with detail on what changed, why, and any required action for users.
Release cadence
We ship on a predictable schedule so teams can plan around updates. No surprise breaking changes during business hours.
- Patch releases: every Tuesday and Thursday (bugfixes, UI polish)
- Minor releases: every 2 weeks (new features, expanded integrations)
- Major releases: quarterly (new modules, redesigned workflows)
- Hotfixes: as needed, outside business hours when possible
How to read a release note
Every entry follows the same format so you can scan fast. Versioning is semver (Major.Minor.Patch).
- Added: new functionality
- Changed: modified behaviour, may need workflow updates
- Fixed: bug fixes with reproduction steps
- Deprecated: features scheduled for removal (90-day window)
- Removed: features that no longer exist (with migration link)
Subscribing to updates
Get notified only about the releases that matter to you. No spam, easy unsubscribe.
- Email digest: weekly summary of all changes
- In-app banner: major releases only, dismissible
- RSS feed: workexe.com/changelog.rss for power users
- Slack/Teams app: per-channel release announcements
Breaking changes policy
We hate breaking things as much as you do. When we have to, you get warning and a migration path.
- Minimum 90 days notice before any API breaking change
- Old endpoints kept alive in parallel during deprecation window
- Migration scripts published for non-trivial schema changes
- Personal email notification to API key owners 30/14/7 days before removal
Where to find specific versions
All releases since v1.0 are archived. URL pattern: workexe.com/changelog/v{X.Y.Z}. SEO-indexed so Google can also help you find a specific change.
- 1Open Project
Launch the changelog and release notes module from your project panel.
- 2Connect Sources
Add GSC, GA4 and any required CSV imports.
- 3Set Scope
Choose location, language, device and alert thresholds.
- 4Validate
Confirm the first scan against a known page or query.
