Skip to content

TautWeekly for Plex v0.12.7

Choose a tag to compare

View all tags
@github-actions github-actions released this 15 Aug 21:46
· 56 commits to main since this release
v0.12.7
c6e6a6e
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

TautWeekly for Plex v0.12.7

v0.12.7 is a focused Windows Setup hotfix for profiles where Windows returns an
empty or invalid per-user Programs shell-folder path. In affected v0.12.5
and v0.12.6 updates, Setup stopped before creating Start-menu shortcuts while
preserving the existing installation, configuration, and history.

Finish updates on affected Windows profiles

Setup now resolves the current user's Start-menu Programs folder through the
native Windows Shell API instead of a PowerShell COM lookup. If Windows still
does not provide a usable path, Setup uses a bounded fallback derived from the
current user's absolute APPDATA or USERPROFILE path.

The fallback is limited to the current user's standard Start-menu hierarchy.
It does not inspect another account, use a public Desktop, or change the
selected application and private-data directories.

Setup also preselects an existing installer-owned application folder more
reliably. If the primary InstallLocation registry value is missing or stale,
it can recover the same validated folder from the registered uninstaller or
application icon. Arbitrary folders are never accepted from registry data: the
candidate must contain TautWeekly installer metadata or a verified portable
release manifest. Legacy BAT-only folders that have never been migrated still
require one explicit selection.

Update from v0.12.6 or the interrupted update

  1. Download TautWeekly-Setup.exe and SHA256SUMS.txt from this release.
  2. Verify the EXE against SHA256SUMS.txt.
  3. Run Setup again and confirm Update for the preselected installation.
  4. Open the Manager and confirm the existing configuration, history, and
    schedule state are present.

No manual cleanup or reconfiguration is required after the reported
resolve Windows Start menu failure. The failed attempt stopped safely before
removing private state.

Validation and limitations

Release validation covers the native and fallback shell-folder paths, Manager
and installer unit tests and vetting, an isolated Windows install/update/icon/
uninstall lifecycle, release archive reproducibility, and maintained Manager
cross-builds for Windows, Linux, macOS, and FreeBSD on amd64 and arm64.

The Setup executable remains unsigned. Windows SmartScreen may identify it as
an unknown publisher; verify the download against SHA256SUMS.txt.

Assets 13
Loading