Getting started
Overview
Understand Release Guard's project release validation, actual-player UI QA, Publisher Mode, reversible fixes, CI evidence, and extension model.
Release Guard is a release decision system for Unity. It evaluates project policy, captures and reviews UI evidence, audits exact customer package roots, applies only explicitly supported reversible fixes, and exports machine- and reviewer-readable evidence.
Decision model
- Project Release evaluates the committed release profile against the selected target and project state.
- UI Release QA reviews structural evidence and actual-player screenshots with explicit baselines, masks, tolerances, geometry, target-size, text, focus, locale, and theme evidence.
- Publisher Mode audits the exact customer package root and keeps local package readiness distinct from missing external marketplace evidence.
- Safe remediation is previewed before mutation, confirmed by the user, and reversible. There is no global blind Auto Fix All.
- CI uses the same committed profiles, rules, capability model, and terminal report contract as the Editor workflow.
Fail-closed capabilities
Required evidence that is unavailable, unsupported, stale, invalid, or blocked is not a pass. Release Guard keeps capability state separate from finding severity so missing evidence cannot be hidden by severity overrides.
Included Core component
Release Guard depends on net.kiwistudios.releasecore 26.8.5 as a bundled internal component. Release Core is hidden from the public package catalog and is not a separately published product.
Start here
- Run the first governed release check
- Capture and review UI evidence
- Audit the exact customer package root
- Gate the same profile in CI
- Add deterministic customer-owned rules
Privacy and network boundary
No account, login, cloud service, or telemetry is required. Network behavior is limited to explicit user-controlled external tooling or absolute URL inputs. Review evidence before sharing it because screenshots, structural text, paths, and project metadata can contain sensitive project information.
Still stuck?
Bring the exact release evidence.
Include Release Guard and Unity versions, the workflow/profile, target, rule IDs, capability states, report identity, and the smallest reproduction.