Update from 3.1.0 to 3.3.0 fails with warning over publisher change

[tmohrlueder]

Hi,

I just tried to go from PnP.PowerShell 3.1.0 to 3.3.0 via "Update-Module PnP.PowerShell" and got the following warning:

Install-Package: A Microsoft-signed module named 'PnP.PowerShell' with version '3.1.0' that was previously installed conflicts with the
new module 'PnP.PowerShell' from publisher 'CN=PNPPowershell (.Net Foundation), O=PNPPowershell (.Net Foundation),
L=Redmond, S=Washington, C=US, SERIALNUMBER=603 389 068, OID.2.5.4.15=Private Organization,
OID.1.3.6.1.4.1.311.60.2.1.2=Washington, OID.1.3.6.1.4.1.311.60.2.1.3=US' with version '3.3.0'. Installing the new
module may result in system instability. If you still want to install or update, use -SkipPublisherCheck parameter.

Is that normal? Should I just go ahead with -SkipPublisherCheck? I did a quick search but couldn't find any information on that. And unexpected certificate changes make me nervous nowadays :)

[tmohrlueder]

The publisher change was mentioned in the blog post of the 3.2.0 release: https://pnp.github.io/blog/pnp-powershell/pnp-powershell-v3-2-0/#-now-part-of-the-net-foundation ... wish this was part of the changelog on GitHub as well, but good enough for me.