As discovered in #10, module manifest validation fails if a module has dependencies, and they aren't installed on the local machine (pretty much always going to be true for the Actions runners that this action will be running on).
As a result, I've disabled module manifest validation when the RequiredModules section of a manifest isn't null. According to https://github.com/PowerShell/PSResourceGet/issues/903, this is planned to be fixed in the future version of PSResourceGet, so I'm adding this as a reminder to re-enable this in the future once PSRG is updated.
As discovered in #10, module manifest validation fails if a module has dependencies, and they aren't installed on the local machine (pretty much always going to be true for the Actions runners that this action will be running on).
As a result, I've disabled module manifest validation when the RequiredModules section of a manifest isn't null. According to https://github.com/PowerShell/PSResourceGet/issues/903, this is planned to be fixed in the future version of PSResourceGet, so I'm adding this as a reminder to re-enable this in the future once PSRG is updated.