-
-
Notifications
You must be signed in to change notification settings - Fork 472
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Certificate warning when upgrading to 5.6.0-beta1 #2438
Comments
There is no solution unfortunately. If I stop signing the certificate there will be warning. If I rename the certificate people won't be able to find it. This will just continue happening if the root will change again in 3 years for new certificate. Unless the logic in powershell changes, and everyone will update. |
This issue does not occur with PSResourceGet. PS C:\> Get-PSResource Pester
Name Version Prerelease Repository Description
---- ------- ---------- ---------- -----------
Pester 5.5.0 PSGallery Pester provides a framework for running…
PS C:\> Update-PSResource Pester -PassThru
Name Version Prerelease Repository Description
---- ------- ---------- ---------- -----------
Pester 5.6.0 PSGallery Pester provides a framework for running… |
IIRC they removed the whole publisher check in v3. Most users still use older out-of-box modules unfortunately. |
It's still there but is now opt in rather than opt out. |
Could there be a notice of this on the readme? i mean it wont really help with the module system being stupid, but it does feel better if the first thing you saw when searching for "pester powershell" be a "please note: certificate from previous versions have changed.." |
Sure, do you want to PR it? |
Pinned issue was a good call. |
We have pinned version for long time, and I get this same cert error. Only way to workaround is by adding -SkipPublisherCheck fixes Install-Module -Name 'Pester' -RequiredVersion 5.3.1 -Force | Out-Null "C:\Program Files\PowerShell\7\pwsh.exe" -NoLogo -NoProfile -NonInteractive -Command D:\a_temp\434bdabc-db7b-4fdc-9743-7ddeeb878098.ps1 |
@RKSelvi Looks like it's because you've already installed 5.6.0 locally. Same issue just different direction, downgrade vs upgrade with mismatching certs. |
Checklist
What is the issue?
The new code signing certificate unfortunately triggers a new publisher warning when calling
Update-Module
Expected Behavior
No warning.
Steps To Reproduce
Describe your environment
Pester version : 5.5.0 C:\Users\Frode\Documents\PowerShell\Modules\Pester\5.5.0\Pester.psm1
PowerShell version : 7.4.2
OS version : Microsoft Windows NT 10.0.22631.0
PowerShellGet version: 2.2.5
Possible Solution?
No response
The text was updated successfully, but these errors were encountered: