|
|
||
|---|---|---|
| .github/workflows | ||
| .gitignore | ||
| README.md | ||
OST-Nightly - cheers claude
Nightly builds of OpenSteam001/OpenSteamTool
(a repo we don't own), compiled from its main branch and published as GitHub Releases here.
We can't add CI to a repo we don't control, so this repo tracks upstream externally: a scheduled
GitHub Action checks out the public upstream at its current main HEAD, builds it with MSVC exactly
the way upstream's own release workflow does (CMake + Ninja Multi-Config, -DOPENSTEAMTOOL_VERSION),
and publishes the binaries.
Hash gate — only builds when upstream actually changed
Every run first resolves upstream main's HEAD commit sha (git ls-remote) and compares it to the
sha recorded in the body of the latest release here (UpstreamCommit: <sha>). If they match, the run
exits early — no build, no new release. A fresh nightly is cut only when upstream moved. Manual
runs can override this (see below).
Release contents
Each release is tagged nightly-<UTCdate>-<shortsha> and carries:
| Asset | Purpose |
|---|---|
OpenSteamTool-<version>-Release.zip |
The three DLLs bundled — one-download install |
OpenSteamTool.dll, dwmapi.dll, xinput1_4.dll |
The same binaries individually, for per-file hash checks |
Each asset's sha256 digest is computed automatically by GitHub.
Running it
- Scheduled: daily at 08:00 UTC (
.github/workflows/nightly.yml). - Manual: Actions → Nightly OpenSteamTool build → Run workflow. Tick force to build even when upstream is unchanged (use this for the first run / to re-test the pipeline).
Disabling
Disable the workflow from the Actions tab, or remove the schedule: trigger in
.github/workflows/nightly.yml (leaving workflow_dispatch for manual builds).
Licensing
These are builds of upstream OpenSteamTool — its LICENSE governs the source and redistribution of
the binaries produced here.