> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lanesync.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Your first release

> Step-by-step walkthrough to advance a milestone from PLANNING through DEPLOYED on LaneSync.

This guide follows a single milestone (`v1.0.0`) through every stage on the **hosted LaneSync SaaS**. Use it after completing the [Quickstart](/quickstart).

## Setup

Create a milestone in GitHub:

* **Title:** `v1.0.0`
* **Issues:** 2–3 issues linked to the milestone (e.g. feature work and a bug fix)

Ensure the repo completed the [repo setup wizard](/guides/install-github-app) so `sdlc.yaml` and CI workflows exist.

## Stage walkthrough

<Steps>
  <Step title="PLANNING → DEVELOPMENT">
    **Gate:** All milestone issues must have assignees.

    1. Open each issue in GitHub
    2. Assign a team member
    3. Refresh the LaneSync dashboard — stage advances to **DEVELOPMENT**

    **Stuck?** See [Troubleshooting — stuck in PLANNING](/reference/troubleshooting#milestone-stuck-in-planning).
  </Step>

  <Step title="DEVELOPMENT → TESTING">
    **Gate:** All issues closed via merged PRs; required CI checks pass on `main`; release branch exists (release-branch mode).

    1. Open PRs that reference and close milestone issues (`Fixes #123`)
    2. Ensure CI passes — check names must match `sdlc.yaml` `development.required_checks`
    3. Merge PRs to `main`
    4. Cut release branch: `git checkout -b release/v1.0.0 && git push -u origin release/v1.0.0`

    **Trunk-based mode:** Skip release branch creation if configured during wizard setup.
  </Step>

  <Step title="TESTING → EVIDENCING">
    **Gate:** Required checks pass on the release branch (or trunk).

    1. CI runs on `release/v1.0.0` automatically
    2. Wait for all checks in `testing.required_checks` to succeed
    3. Evidence upload step runs on release branch pushes (bootstrapped workflow)

    LaneSync marks only **required** checks as blocking when they fail.
  </Step>

  <Step title="EVIDENCING → DEPLOYMENT">
    **Gate:** Required artifacts uploaded; evidence PR approved.

    1. Verify test artifacts appear in stage details
    2. Open the evidence PR (created by CI or manually)
    3. Request review from `engineering-leads` (or configured team)
    4. Approve from [lanesync.dev](https://lanesync.dev) dashboard or GitHub

    See [Evidence approval](/guides/evidence-approval) for reviewer configuration.
  </Step>

  <Step title="DEPLOYMENT → DEPLOYED">
    **Gate:** Manual production promotion after deploy gate passes.

    1. Confirm deploy gate: `can_deploy: true` for version `v1.0.0`
    2. Trigger production deploy (your existing deploy workflow or manual process)
    3. LaneSync records deployment and marks milestone **DEPLOYED**
  </Step>
</Steps>

## Monitor progress

| Tool                                           | Use                                              |
| ---------------------------------------------- | ------------------------------------------------ |
| [lanesync.dev](https://lanesync.dev) dashboard | Stage pipeline, blocking items, drill-down links |
| Milestone stage details                        | Live `sdlc.yaml`, per-check status               |
| GitHub                                         | Issues, PRs, workflow runs                       |

The dashboard auto-syncs every 60 seconds. Webhook events trigger faster updates via server-sent events.

## Demo shortcut (development only)

Self-hosted and local environments expose a demo setup endpoint. **Not available on hosted SaaS:**

```bash theme={null}
curl -X POST https://your-instance/api/sync/setup-demo/<owner>/<repo>
```

Hosted customers should create milestones directly in GitHub or via the dashboard.

## Next steps

* [Configure sdlc.yaml](/guides/configure-sdlc-yaml) for your team's checks and reviewers
* [CI evidence upload](/guides/ci-evidence-upload) to customize pipeline integration
* [Project roll-ups](/guides/project-rollups) for multi-repo releases