Lataa SysManager 1.113.4

[1.113.4] - 2026-09-24
The About tab now marks the version you are running in its list of releases. A "Current" badge was
always meant to sit on that entry, and the README has described it since v1.85.0, but it had never once
appeared: the check behind it compared two versions that could not match. It does now.
Fixed
- The "Current" badge in the About tab's release list now appears on the release you are running. It
had been missing since the tab was added in v0.5.0. Each entry's version is read from its release tag,
which has three parts (1.113.4, say), while the running app's version comes from the build and always
carries a fourth part of zero (1.113.4.0). The comparison counted that missing fourth part as different
from zero, so no entry ever matched. Versions are now compared as the release they name, however many
parts they are written with. The check that decides whether an update is newer uses the same
comparison, so the two can never disagree about a pair of versions, and it gives the same answer as
before for every version SysManager has published.
- The text on the About tab's version badge is readable on every colour theme. It was fixed white,
which falls short of the 4.5:1 contrast small text needs on ten of the twelve built-in themes — 2.15:1 on
Warm Ember, and just under the line at 4.47:1 on the default, Midnight Indigo. It now uses the colour the
primary buttons already use, chosen per theme for contrast: dark on most themes, including the default,
and white on Soft Blossom and Lavender. The newly visible "Current" badge uses it as well. The change
that moved the rest of the app to that colour (#2012) only looked at the shared styles, which is how two
badges placed directly on the About page kept their white text; the automated check now looks at every
page too.
Verify the download
Get-FileHash .\SysManager-v1.113.4.exe -Algorithm SHA256
Expected SHA256: BB16A1993ED8C1B91C272F628596A9EF217248FA072572CE0C8A68216E73294A
This build is not code-signed, so Windows will warn on first launch. That is
expected for a small independent app: see what the warning says and what to
click.
Code signing is planned through the SignPath Foundation,
which provides free certificates to open-source projects, with signing performed by
SignPath.io. Until then, the SHA256 above and the build
attestation below are what establish that a download is the genuine build.
Code signing policy
This release is not code-signed. The team roles, release-approval process and
privacy policy required by the SignPath Foundation programme
are documented in advance under Code signing
policy. That
documentation is a prerequisite for applying, not evidence of a certificate. The
attribution line naming SignPath as the signing provider will appear here once a
certificate is actually issued.
This program will not transfer any information to other networked systems unless
specifically requested by the user or the person installing or operating it. Full
privacy policy.
Verify where this binary came from
This exe was built by GitHub Actions from this public source, and the build is
recorded in the Sigstore public transparency log. With the
GitHub CLI:
gh attestation verify .\SysManager-v1.113.4.exe --repo laurentiu021/SystemManager
That proves which commit and workflow produced this exact binary, something the
SHA256 file cannot show, since it is published alongside the exe it describes.
Each release also ships SysManager-v1.113.4.sbom.json, a CycloneDX inventory of
every dependency resolved for this build.