Use case
Concepts
Create a project
1
Open Projects
In lanesync.dev, navigate to Projects in the sidebar.
2
Create release project
Click New project. Enter name (e.g.
Platform v2.4.0) and optional target date.3
Link milestones
Add milestones from each microservice repository. Each linked milestone should use a consistent version label (e.g.
v2.4.0).4
Monitor aggregate status
The project dashboard shows per-service stage pipelines and highlights blocking services.
API
Projects are managed via/api/projects:
Session authentication required. See API Reference.
Best practices
Align version labels
Align version labels
Use the same semver across services (
v2.4.0) so stakeholders recognize one release train.Define a critical path
Define a critical path
Mark blocking services in your release process. Roll-ups surface which repo is furthest behind.
Pair with evidence approval
Pair with evidence approval
Each service still completes its own EVIDENCING gate. Roll-ups do not bypass per-repo enforcement.
Limitations
- Roll-ups are visibility and coordination — enforcement remains per-repository via
sdlc.yaml - A project cannot advance a milestone on your behalf; teams still merge, test, and approve per repo
Related
- Dashboard overview — org-wide milestone view
- Your first release — single-repo walkthrough