Start Here

How to Sign Builds in CI/CD

A practical, beginner-friendly guide to how to sign builds in ci/cd for independent software developers preparing a trustworthy NeonRoof release. It covers the decisions, evidence, and release checks that matter in start here.

Release checklist

  1. Create or sign in to the shared NeonRoof developer account.
  2. Complete the studio profile, contact details, identity checks, and payout setup when selling software.
  3. Prepare listing copy, licensing details, support links, artwork, screenshots, and a release package.
  4. Submit the exact release for security and certification review.
  5. Publish after approval, then monitor downloads, reviews, comments, updates, and support requests.

How to apply this on NeonRoof

Prepare the evidence while you build the release, not after uploading it. Enter the same publisher name, version, architecture, licensing details, and support information everywhere. Submit one final binary, then wait for release-specific certification before making it downloadable.

If a check fails, correct the source or packaging process, increment the release when appropriate, build again from a known revision, and submit the new immutable binary. Never replace a certified file behind the same URL.