Skip to main content
This guide follows a single milestone (v1.0.0) through every stage on the hosted LaneSync SaaS. Use it after completing the Quickstart.

​
Define the release in LaneSync

Complete the repository setup wizard first. Release creation checks access to the repository in your workspace and verifies configuration and active protection before writing to GitHub.
1

Define release

In Releases, click New release and select a configured repository. Enter a version such as v1.0.0, optional description and target date, or choose an existing open GitHub milestone. You can optionally associate the release with a project.
2

Choose scope

Select existing open issues available for the release, or create new issues. Issues belonging to another milestone are unavailable for a new release. Review missing owners before continuing. Creating the same release across several repositories uses new issue drafts rather than moving issues between repositories.
3

Review and save

Review the repository, release definition, scope and owners. Back retains your input. Save once and wait for the result; the dialog prevents repeated submission while the request is pending.If only part of the operation succeeds, inspect the saved milestone and reported progress before creating again. A saved release with a failed project association offers a separate retry for that association.
Creating a release milestone does not deploy it. Its readiness is evaluated against the repository’s sdlc.yaml as work progresses.

​
Stage walkthrough

The examples below use main and release/v1.0.0. Use the branch names, release model, checks and reviewer policy configured in your repository’s sdlc.yaml.
1

PLANNING → DEVELOPMENT

Gate: The configured planning requirements pass, including issue ownership when required.
  1. Open the release’s Scope & owners tab
  2. Assign owners or use Assign to me for your work
  3. Review readiness after the save; advancement depends on the configured planning requirements
Stuck? See Troubleshooting — stuck in PLANNING.
2

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. After CI succeeds on the development branch, LaneSync creates a dev-{short-sha} tag. No repository secrets are required
  5. Use Cut release branch in the release header when LaneSync makes it available. Review the result before advancing to testing.
Wizard trunk mode (no release branch): skip step 5. Testing stays on the development branch; only dev-* tags are created.
3

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. After that push succeeds, LaneSync creates v1.0.0-rc-{short-sha} — this is the release-candidate commit later promoted to v1.0.0
  4. Evidence upload step runs on release branch pushes (bootstrapped workflow)
LaneSync marks only required checks as blocking when they fail. Tags are created for LaneSync CI templates (ci.yml / ci-*.yml). If you brought your own CI, add equivalent tags yourself.
4

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 dashboard or GitHub
See Evidence approval for reviewer configuration.
5

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

​
Monitor progress

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

​
Next steps