We shipped a large platform update across UI, API, and deployment architecture. This release includes breaking changes for some existing workspaces and integrations.
If you have older projects, please read the migration section below before continuing normal edits.
What changed (high level)
- New workspaces are now empty by default (no pre-created lanes).
- Default view changed to List instead of Timeline.
- Lane deletion is now supported via API with conflict handling.
- Timeline short-item filtering moved to workspace-level setting (`timelineMinDurationDays`, default 7, minimum 1).
- UI and worker deployment model was split and hardened to avoid cross-deploy incidents.
Breaking changes
The following are the important compatibility changes:
- Workspace bootstrap behavior changed: integrations that assumed default lanes (for example “Backlog”, “In Progress”, “Done”) must now create lanes explicitly.
- Default UX entry point changed: new workspaces open in List view by default.
- Timeline rendering logic changed: items shorter than workspace threshold can be hidden from timeline while still existing in board/list.
Migration guidance for older projects
- Open each legacy workspace and verify lane structure explicitly.
- If your automation creates items, ensure lanes are created first.
- Check timeline visibility setting (`timelineMinDurationDays`) for stakeholder views.
- Update any scripts that assumed timeline-first default behavior.
API updates
The API now includes lane deletion and workspace settings endpoints, in addition to existing item, journal, and decision endpoints.
- API docs: https://easyroadmap-api.easyroadmap.workers.dev/api/docs
- OpenAPI JSON: https://easyroadmap-api.easyroadmap.workers.dev/api/docs/openapi.json
Rollout approach
We are rolling out this version in phases. First, our own team validates the new behavior in real workflows, including AI-agent assisted planning and API-driven editing scenarios.
After internal validation, we expand usage to broader project types and monitor migration outcomes before treating the release as fully stable for all legacy setups.
Deployment and SEO hardening
We also fixed a production issue where UI and worker deployments could target the wrong runtime. Deployment is now separated into independent workflows, and canonical redirects normalize host/scheme/path variants.
Questions or migration help?
If your existing projects behave differently after this update, contact us with your workspace ID, expected behavior, and current API flow. We can help map old assumptions to the new model quickly.