Validate Unity Addressables content updates before upload and check the files older players still need after deployment.

ARGUS Release Guard is a Unity Editor tool for teams that publish remote Addressables content. Compare a candidate build with your live release, review potential compatibility problems and download impact, then verify required files on your content host.

- Check your next content release

• Confirm the expected production profile and build target.
• Detect unresolved remote paths and unexpected changes to remote load locations.
• Check expected catalog and hash companion artifacts.
• Find missing bundle artifacts and dependency references that point to absent bundles.
• Check content update restrictions against the previous build’s content state.
• Review changed bundles, shared dependency churn and estimated download impact against configurable thresholds.
• Keep historical releases in a protected baseline set and check remote artifacts those releases still require.

- Four ways to validate

1. Quick Preflight
   Review project and Addressables configuration without creating a new content build. Use it for early checks; it does not replace full release validation.
2. Deep Pre-upload
   Compare a candidate Addressables build against your primary baseline and configured protected baselines before uploading content. Review catalogs, bundles, dependencies, profile and target consistency, content update restrictions and download impact.
3. Post-upload
   Check whether required candidate and protected-baseline artifacts are reachable at their expected remote URLs. Verification uses bounded HTTP requests and does not download entire bundles. Timeouts, authentication failures and other uncertain responses remain unresolved rather than being reported as missing files.
4. CI / Batch Mode
   Run the same validation engine through Unity batch mode. Export JSON, Markdown and JUnit XML reports and use exit codes to gate your release pipeline.

• Findings you can investigate

Each finding includes a rule ID, severity, supporting evidence, an explanation and a recommended next step. Reports distinguish blocking problems, warnings and checks that could not be evaluated.

Results are PASS, PASS_WITH_WARNINGS, BLOCKED or INCONCLUSIVE. When required evidence is missing or fails to collect, ARGUS does not silently approve the release. Download estimates remain explicitly partial when the available evidence cannot establish bundle reuse.

• Built for your existing workflow

Install the UPM package and open Tools > ARGUS Release Guard. Capture a baseline from a known release, configure your production profile and policies, build your candidate content, and run the appropriate validation mode. For content updates, keep the previous build’s addressables_content_state.bin available.

ARGUS runs in the Editor and adds no runtime assemblies to your player. It does not upload or delete content, rewrite catalogs, or change Addressables profiles or groups. It uses no ARGUS cloud account, backend or telemetry service. Remote verification contacts the content endpoints configured in your project.

• Requirements and scope

Supported editor families are final Unity 2022.3 LTS and Unity 6 (6000.x) releases, with the Addressables versions listed in the compatibility documentation. Built-in JSON and binary catalog outputs are supported. Check the compatibility matrix for supported package families and tested combinations.

ARGUS analyses configuration and build evidence and checks remote artifact availability. It does not simulate players or verify runtime loading behavior. Catalog contents and binary bundle payloads are not parsed for semantic correctness. macOS and Linux Editor environments are currently unverified.

[Documentation and compatibility]

[Support]