New version: ptweezy.cronstable version 1.2.49

[ptweezy (ptweezy)]

📖 Description

✅ Checklist

• Signed the Contributor License Agreement
• Linked to an issue (if applicable)
  • Resolves #[Issue Number]

📦 Manifest Checklist

• Checked that there aren't other open pull requests for the same manifest update/change
• This PR only modifies one (1) manifest
• Validated manifest locally with winget validate --manifest <path> (validation guide)
• Tested manifest locally with winget install --manifest <path>
• Manifest conforms to the 1.12 schema

Note: <path> is the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

[ptweezy (ptweezy)]

Author check-in. What run WinGetSvc-Validation-426569-1's artifact zip shows:

x64, Validation-Installation-Error, exit code -2145844744 (0x801901F8, HTTP_E_STATUS_GATEWAY_TIMEOUT): the VM could not download the installer. The WinGet client log shows DeliveryOptimization failing with 0x801901f6 and the WinINet fallback receiving HTTP 504 from the GitHub release URL, on both attempts. The URL downloads normally today and its SHA256 matches the manifest, so this was a transient CDN failure during the run.

arm64, Validation-Executable-Error (ManualReview): the launched-exe check ran cronstable.exe with no arguments. cronstable is a CLI scheduler; with no configuration present it prints a config-not-found hint plus usage and exits 1 by design, the same behavior as the merged versions through 1.2.41. cronstable --version exits 0 and prints 1.2.49.

The x64 image's own Defender also could not update during the run: MpCmdRunupdate.log shows signature version 1.455.28.0 and Signature Update failed with hr=0x80070652.

Could a moderator rerun validation for the x64 download flake, and consider Manual-Validation-Completed for the arm64 executable check? Both installers are Authenticode signed, and every InstallerSha256 in this PR matches the release's published SHA256SUMS.

[Demitrius Nelon (denelon)]

wingetbot (@wingetbot) run