windows based builds using Pester fail with certificate mis-match error
techthoughts2 opened this issue · comments
Jake Morrison commented
Expected Behavior
Windows based builds should run without an error
Current Behavior
Install-Package: Authenticode issuer 'CN=Jakub Jareš, O=Jakub Jareš, L=Praha, C=CZ' of the new module 'Pester' with version '5.5.0' from
root certificate authority 'CN=DigiCert Assured ID Root CA, OU=www.digicert.com, O=DigiCert Inc, C=US' is not matching
with the authenticode issuer 'CN=Jakub Jareš, O=Jakub Jareš, L=Praha, C=CZ' of the previously-installed module 'Pester'
with version '5.6.1' from root certificate authority 'CN=DigiCert Trusted Root G4, OU=www.digicert.com, O=DigiCert Inc,
C=US'. If you still want to install or update, use -SkipPublisherCheck parameter.
Possible Solution
Likely related to: pester/Pester#2438
Steps to Reproduce
- Any project with a windows based build
- Trigger build
Detailed Description
Windows based builds are failing with a Pester certificate warning. This is likely due to the windows build container containing an older version possibly of the pester cert and not liking the new certificate mis-match. Linux and MacOS are not affected as they have no previous version of Pester in the default container image.