Skip to content

winunitd 0.5.1

Latest
Latest

Choose a tag to compare

View all tags
@github-actions github-actions released this 19 Oct 19:11
· 13 commits to main since this release
Immutable release. Only release title and notes can be modified.
v0.5.1
8323f6c
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

winunitd 0.5.1

This patch fixes repeated installation and lifecycle behavior. For Windows
11 Enterprise and Enterprise LTSC x64; no Go or .NET runtime is needed on the
destination.

The MSI is not code-signed yet, so Windows SmartScreen may warn when you open
it. Check the download against this release's SHA256SUMS and build provenance:

Get-FileHash .\winunitd-0.5.1-x64.msi -Algorithm SHA256
gh attestation verify .\winunitd-0.5.1-x64.msi --repo PLN/winunitd `
  --signer-workflow PLN/winunitd/.github/workflows/release.yml `
  --source-ref refs/tags/v0.5.1

Install or upgrade

From an elevated terminal:

msiexec /i .\winunitd-0.5.1-x64.msi /qb

Over 0.5.0 this upgrades in place: the service stops, the new version starts,
and units, enablement, logs and linger grants carry over. See the
installation guide
for installation and earlier package upgrades.

Fixes since 0.5.0

  • Repeating installation of the exact installed MSI restores a service that
    was running before the command. A previously stopped service remains stopped
    on a plain repeat install.
  • When a process exits and its replacement fails to start, Start and Status
    report failure and the launch error instead of stale active/running status
    with no main process.
  • Daemon verification rejects User= in user-manager units, matching reload
    and file verification.
  • Daemon shutdown no longer reports a cleanup failure if a child exits between
    the liveness check and termination. Failed termination of a still-running
    child remains visible.

Limits

Support and limitations remain as documented for
0.5.0.
Signing remains deferred.

Qualification

Windows and Linux CI passed on the release source. Before publication, the
actual hosted MSI passed clean installation, same-package installation with
the service initially running and stopped, a cold boot with the enabled worker
returning automatically, and uninstall with retained data. An upgrade from the
public 0.5.0 MSI preserved the worker unit files and enablement, returned the
service and worker, and left only the new product registration; uninstall
passed afterward. Checksums, the clean package manifest and both hosted build
attestations were verified against the exact release tag.

Assets 6
Loading