New version: Friction.Friction 0.9.6.1

[kris6673]

Resolves: #196208

Microsoft Reviewers: Open in CodeFlow

[wingetbot]

   

[wingetbot]

/AzurePipelines run

[wingetbot]

Url Validation Error

• manifests\f\Friction\Friction\0.9.6.1
  • https://friction.graphics/documentation/shaders/
    • Http status code: NotFound

[wingetbot]

/AzurePipelines run

[stephengillie]

Automatic Validation ended with:

Installation failed with exit code -1978334972
2025-01-09 07:46:35.023 [CLI ] No suitable installer found for manifest Microsoft.VCRedist.2015+.x64 with version 14.42.34433.0

Automated error analysis suggests -1978334972 may mean This package has a dependency missing from your system.

(Automated response - build 937.)

[kris6673]

Automatic Validation ended with:

Installation failed with exit code -1978334972
2025-01-09 07:46:35.023 [CLI ] No suitable installer found for manifest Microsoft.VCRedist.2015+.x64 with version 14.42.34433.0

Automated error analysis suggests -1978334972 may mean This package has a dependency missing from your system.

(Automated response - build 937.)

The dependency is in the manifest and installs correctly when testing with sandboxtest.ps1:

[wingetbot]

/AzurePipelines run

[wingetbot]

/AzurePipelines run

[kris6673]

I really don't agree with it missing a dependency, and it installs correctly with the current manifest

Automatic Validation ended with:

Installation failed with exit code -1978334972
2025-01-09 07:46:35.023 [CLI ] No suitable installer found for manifest Microsoft.VCRedist.2015+.x64 with version 14.42.34433.0

Automated error analysis suggests -1978334972 may mean This package has a dependency missing from your system.
(Automated response - build 937.)

The dependency is in the manifest and installs correctly when testing with sandboxtest.ps1:

[stephengillie]

Sorry for the misleading error messages. This is a pipeline "misconfiguration", where it strictly requires that dependency scope and architecture exactly match the main package. But your validation environment isn't bound by this, nor is mine. So the fix is for me to manually install and scan this in a VM, then update the PR accordingly.