New Version: Astronomer.Astro version 1.41.0

[pritt20]

Checklist for Pull Requests

• Have you signed the Contributor License Agreement?
• Is there a linked Issue? If so, fill in the Issue number below.
  • Resolves #[Issue Number]

Manifests

• Have you checked that there aren't other open pull requests for the same manifest update/change?
• This PR only modifies one (1) manifest
• Have you validated your manifest locally with winget validate --manifest <path>?
• Have you tested your manifest locally with winget install --manifest <path>?
• Does your manifest conform to the 1.12 schema?

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

---

Microsoft Reviewers: Open in CodeFlow

[wingetbot]

Validation Pipeline Run WinGetSvc-Validation-138-360790-20260414-1

[stephengillie]

Automatic Validation ended with:

Installation failed with exit code -1978334972
2026-04-14 09:54:39.998 [CLI ] No suitable installer found for manifest RedHat.Podman with version 5.8.1

Hex	Dec	Inverted Dec	Symbol	Description
8A150104	-1978334972	2316632324	APPINSTALLER_CLI_ERROR_INSTALL_MISSING_DEPENDENCY	This package has a dependency missing from your system. (The most common dependency is Microsoft.VCRedist.2015+.x64 / .x86)

(Automated response - build 1247.)

[DandelionSprout]

Removing the InstallerLocale: en-US line from the manifest will likely bypass the error.

[wingetbot]

Validation Pipeline Run WinGetSvc-Validation-140-360790-20260415-1

[pritt20]

Removing the InstallerLocale: en-US line from the manifest will likely bypass the error.

Hey @DandelionSprout @stephengillie

I removed InstallerLocale: en-US line from the manifest and validation is still failing in CI job.

Could this be related to issue #152555 instead?

[DandelionSprout]

Considering RedHat.Podman has Scope specified upstream, then probably yes.

[wingetbot]

Validation Pipeline Run WinGetSvc-Validation-140-360790-20260415-2

[wingetbot]

Validation Pipeline Run WinGetSvc-Validation-140-360790-20260417-1

[stephengillie]

Automatic Validation ended with:

Installation failed with exit code -1978334972
2026-04-17 04:19:13.223 [CLI ] No suitable installer found for manifest Podman.CLI with version 5.8.1

Hex	Dec	Inverted Dec	Symbol	Description
8A150104	-1978334972	2316632324	APPINSTALLER_CLI_ERROR_INSTALL_MISSING_DEPENDENCY	This package has a dependency missing from your system. (The most common dependency is Microsoft.VCRedist.2015+.x64 / .x86)

(Automated response - build 1248.)

[pritt20]

Automatic Validation ended with:

Installation failed with exit code -1978334972
2026-04-17 04:19:13.223 [CLI ] No suitable installer found for manifest Podman.CLI with version 5.8.1

Hex Dec Inverted Dec Symbol Description
8A150104 -1978334972 2316632324 APPINSTALLER_CLI_ERROR_INSTALL_MISSING_DEPENDENCY This package has a dependency missing from your system. (The most common dependency is Microsoft.VCRedist.2015+.x64 / .x86)
(Automated response - build 1248.)

Thanks @stephengillie !

I have tested the package locally with both Redhat.podman and Podman.CLI as dependency using command winget install --manifest <path> and It works with both of these dependencies. Could this be CI pipeline validation specific issue?

[pritt20]

Hey @stephengillie,

Could you please help with this validation issue? we are looking to get this one in as soon as possible because this is a blocker for downstream changes.

[pritt20]

Hey @stephengillie,

Would appreciate your help on this one. I need to get this one in to unblock downstream changes.

[stephengillie]

Hi @pritt20,

I'm just seeing this, will run ASAP once I have a free VM.

Edit:

I have tested the package locally with both Redhat.podman and Podman.CLI as dependency using command winget install --manifest and It works with both of these dependencies. Could this be CI pipeline validation specific issue?

Yes, it's part of #152555 - the issue here is that the validation pipelines actually install depenencies in a separate process before the main install, to better separate these processes for scanning and logging. We've identified the cause for the bug, and a fix is in the process of being added to the pipelines.

[wingetbot]

Publish pipeline succeeded for this Pull Request. Once you refresh your index, this change should be present.