Skip to main content
Open Releases at lanesync.dev to answer whether a release can ship and what needs to happen next.
  • Releases lists active releases, their readiness, and a link to the next action. Summary counts show Blocked, Needs approval, and Ready to deploy.
  • Orgs & Repos lists organizations, accessible repositories, and setup choices. Use Discover repositories after changing GitHub App access.
  • Projects groups releases across repositories.
  • My reviews shows pending evidence reviews and your verified eligibility.
  • Quality reports provides quality metrics, report detail and exports.
  • History lists recorded shipped releases with repository and UTC date filters.
  • Settings contains workspace configuration and administration.
Use New release to define a release and choose its scope. See Your first release.

​
Understand readiness

In progress means work or validation remains. Blocked means a required gate or repository setup needs attention. Needs approval indicates evidence awaiting review. Ready to deploy means the release is awaiting production deployment; it does not mean it has shipped. Successful production deployment is recorded separately as Deployed. Open the release to see the blocker and next action. Quality Gates explain their GO or NO-GO verdict with test, coverage, and security evidence. A GO does not finish a required evidence review or merge; those requirements must complete before the release is Ready to deploy. Missing required results never count as a pass. The product tour shows this sequence with illustrative data. Open View readiness to inspect the retained five-stage pipeline: Planning → Development → Testing → Evidencing → Deployment. The Next action card points to the relevant task rather than requiring you to infer it from the stage alone.

​
Repository setup comes first

A setup PR, saved configuration or milestone alone does not establish readiness. LaneSync checks configuration presence and branch protection separately.
Continue the repository wizard. Review and merge the setup PR when requested, then complete protection configuration. A merged PR alone does not prove protection is active.
Inspect the repository configuration and complete the setup action. Routine reads do not reactivate deliberately disabled protection.
LaneSync cannot confirm the required setup observation. Check GitHub App access and retry. Permission failures or outages are not proof that configuration was deleted.
An active release whose setup is incomplete cannot claim In progress or Ready to deploy. A historical deployed release remains a deployment record even if the repository later needs setup attention. Configured repositories may also offer Update LaneSync workflows when managed templates have newer revisions.

​
Refresh and display preferences

Webhooks notify the active workspace through a shared live connection. Polling provides a fallback, and background reconciliation repairs missed setup observations. If newly accessible repositories are absent, verify the installation’s access in GitHub and select Discover repositories. Use the header’s Dark or Light button to switch themes. The original LaneSync symbol and wordmark remain visible in either theme. Workspace data is scoped to your selected organization.

​
Discover newly added repositories

Click Discover repositories to refresh the repository list for the selected workspace. LaneSync uses that workspace’s saved GitHub App installation and its Full or Lite tier, and reads every page of accessible repositories. The action starts repository synchronization in the background. Open Manage repositories & setup to review newly discovered repositories and finish setup. Discovery does not grant access to repositories on GitHub; see Adding repositories later for the access steps.

Release details

Inspect gates and manage scope and owners.

Reviews and history

Check reviewer policy and recorded deployment evidence.