Skip to content

ReleaseGuard v0.1.0-alpha

Latest
Latest

Choose a tag to compare

View all tags
@github-actions github-actions released this 21 Oct 20:23
· 18 commits to main since this release
v0.1.0-alpha
8c4baaa

ReleaseGuard 0.1 Alpha

Windows app

ReleaseGuard-0.1.0-alpha-win64.zip is a self-contained Windows build and needs no Python. Extract it and double-click ReleaseGuard.exe for a guided check, or run the same CLI from PowerShell. The executable is unsigned; verify its SHA-256 from ReleaseGuard-0.1.0-alpha-win64-SHA256SUMS.txt before allowing it past SmartScreen.

ReleaseGuard is an early developer-tool prototype for combining game-authored
save, stability, timing, and packaged-build checks into one local/CI
release-readiness gate. It runs without a hosted service or runtime
dependencies.

Included demonstrations

  • examples/save-corruption-detection.json deliberately interrupts an unsafe
    synthetic save write and passes only when the harness detects the unreadable
    save.
  • examples/save-recovery.json interrupts an atomic replacement and checks
    that the previous committed synthetic save remains readable.
  • releaseguard analyze inventories packaged builds and can enforce size and
    growth limits.
  • releaseguard release-check runs build review and one or more trusted test
    scenarios together, then emits a combined pass/fail JSON report. Scenario
    steps can enforce duration budgets; this is not a frame-time or GPU profiler.
  • releaseguard save can locate a small set of common game saves and create,
    verify, or restore local snapshots. This is an experimental player utility.
  • The self-contained Windows executable provides the same CLI plus a guided
    first run; it is not a GUI.

Requirements

  • Windows 10/11 x64 with no Python needed (win64 ZIP), or Linux with Python 3.10 or newer

The automated test matrix passes on Windows and Linux with Python 3.10 and
3.14. See FIRST-TEST.md for a short synthetic-data test.

Limits

This alpha is not a Unity/Unreal plugin and has not been integrated with a
commercial game. A game team must provide commands for its test build,
representative stability/performance scenarios, and a game-specific save
validator. ReleaseGuard cannot infer whether an arbitrary proprietary save is
logically valid, diagnose all crashes, profile GPU/frame performance, or
automatically optimize the game. Inspect scenario manifests before running
them; they execute the commands listed in the manifest.

When reporting a problem, share redacted logs only. Do not attach save files,
snapshots, unreleased builds, credentials, or reports containing private paths.

Assets 7
Loading