Open marcinsmialek opened 5 months ago
In the thread you reference, the parameter -SkipPublisherCheck is mentioned as a workaround for this issue with Install-Module
.
About publishing the latest version: I would love to! For that I need Windows, though. (Couldn't make Publish-Module work last time I tried on Linux). I don't use Windows anymore. If you happen to have a spare Windows license key that you can give to me, I can try to install Windows 11 in a VirtualBox VM and publish from that (or a container could work? Does Publish-Module work from containers? It's been so long since I played with docker that I forgot how licensing on containers even works...). How much does Windows 11 cost now? Way too much, for sure. I should google or ChatGPT some of this... Or do I still have access to a license through some subscription? hm, I will try to remember to check if I can get a license somehow. I used to have some subscription. I have several modules that need updating in the PSGallery...
Can you publish the current version 1.3.2 to the PowerShell Gallery?
It will need to be signed too to use with the latest PowerShell 7.4.1 and PowerShellGet / Microsoft.PowerShell.PSResourceGet 1.0.4.1 and 1.1.0-preview1, no matter what Execution Policy is set - https://github.com/PowerShell/PowerShellGet/issues/48