/AzurePipelines run

For moderators

This account is automated by Github Actions and the source code was created by CoolPlayLin. If you have any questions about any pull request, don't hesitate to ping @Exorcism0666, I'll get a notification.

良い一日をお過ごしください！

@wingetbot run

Commenter does not have sufficient privileges for PR 135678

/AzurePipelines run

/AzurePipelines run

/AzurePipelines run

Automatic Validation ended with:

(Automated response - build 796.)

Manual Validation ended with:

Manual validations are on 64-bit OSes, so changing the architecture from x86 to x64 won't impact this, as it's already running on x64. I believe what's needed is to change the architecture to arm or arm64, but then we won't have a pipeline that can validate it.

/AzurePipelines run

@Trenly @stephengillie is there now a arm64 validation pipeline with maybe Win11 24H2? Users of the new Snapdragon X Elite laptops may want to use arm64 version of cpu-z

@ Trenly @ stephengillie is there now a arm64 validation pipeline with maybe Win11 24H2? Users of the new Snapdragon X Elite laptops may want to use arm64 version of cpu-z

Unfortunately not currently, but I'll bring the increasing demand for this architecture to the team.

Hi @MagicAndre1981,

We can only provide pipelines for the images made available to us by DaaS. Unfortunately, they don't currently have any arm nor arm64 images.

[Policy] Blocking-Issue

I'm going to go ahead and close this since the schema version is pretty far behind. I don't see any reason not to add the arm64 installer to the existing CPUID.CPU-Z package unless the versions are just completely different.

I don't see any reason not to add the arm64 installer to the existing CPUID.CPU-Z package unless the versions are just completely different.

the versions are completely different

Bummer :(

I'll reach out to @stephengillie to see if I can find a way for him to validate arm64 packages manually. We're working with the infrastructure team to have support for automated validation. I don't have a date yet, but they know it's both important and urgent.

In the mean time, if you want to create a PR for the latest version of the package using the current schema version and @mention me, I'll attempt to manually validate it.

Manifest fields generally stay the same as versions increase - new versions usually add new fields instead of modifying existing ones. So in most cases, just incrementing the ManifestVersion is enough to satisfy the requirement.